Introduction

Npm Package Library:- https://www.npmjs.com/package/userinfo-token-validator

How to run:

Copy the latest token and lan id fromAMP session and paste it on tokenValidator-test.js file on this variables

1.const userinfoUrl = "https://internal.mcc.api.mayo.edu/oauth/userinfo"; 2.const token = ""; 3.const lanId = "";

to test the library run node tokenValidator-test.js it should give you the response of list of group user associated with and validate userbased on token nd lanId

Permissions

Only npm users listed as maintainers of this package can publish updates. Permissions are managed on npmjs.com under the package’s Maintainers settings. (https://www.npmjs.com/package/userinfo-token-validator - see "Collaborators")

If you receive a 403 error while publishing:

• Ensure you are logged in with npm whoami
• Confirm you are listed as a maintainer
• Verify the version number has been updated

Steps to build and Publish NPM package

1. Update Version: Before publishing an update, make sure to update the version number in package.json. You can do this
   manually or using npm: npm version patch # For patch updates (1.0.0 → 1.0.1) npm version minor # For minor updates (1.0.0 → 1.1.0) npm version major # For major updates (1.0.0 → 2.0.0)

2. Build Your Package: If your package requires a build step (e.g., transpiling TypeScript, bundling, etc.), make sure to include a build script in your package.json:

3. Publishing the Package Login to npm: Make sure you are logged in to npm on same terminal of your package: npm login

4. Publish Your Package: Finally, to publish your package to the npm registry, use: npm publish

   Updating the Package Update Dependencies: If you have dependencies to update, you can update them using: npm update

   Update the Package on npm: After making changes, increase the version number as described above, rebuild if necessary, and
   publish again using:npm publish

5. Tagging (Optional) If you want to publish under a specific tag (e.g., for beta versions): npm publish --tag beta

6. Troubleshooting If you encounter permission issues: sudo npm publish If you need to force-publish: npm publish --force