Validate Azure AD Token No Scope

---

What I changed from the base branch: A client_credential does not have to have a scp key on the JWT so I am removing that check to allow service-to-service tokens to be validated.

---

This is a function that can be used to validate an access token received from Azure Active Directory. It is particularly useful when you're using a MSAL library to authenticate users on the frontend and you want to verify Microsoft tokens in the API.

Documentation

For more information about the required props to validate your token and the library itself, please refer to the API Documentation

Installation

1  yarn add validate-azure-ad-token
2  npm install validate-azure-ad-token

Validation Steps

1. Verify if all required props are passed in.
2. Decode the token using the jsonwebtoken library.
3. Send a request to https://login.microsoftonline.com/{tenantId}/discovery/keys?appid={applicationId} to receive all public keys unique to your applicationId and tenantId. This action is cached after one successful attempt.
4. Verify all required access token claims: aud, tid,iss,scp, appid, exp.
5. If the comparison succeeds, the token is valid.

Example

1const validate = require('validate-azure-ad-token').default;
2
3try {
4  const decodedToken = await validate('YOUR_MICROSOFT_ACCESS_TOKEN', {
5    tenantId: 'YOUR_TENANT_ID',
6    audience: 'YOUR_AUDIENCE_ID',
7    applicationId: 'YOUR_APPLICATION_ID',
8    scopes: 'YOUR_SCOPES', // for example ["User.Read"]
9  });
10
11  // DO WHATEVER YOU WANT WITH YOUR DECODED TOKEN
12} catch (error) {
13  // ALL ERRORS GONNA SHOW HERE AS A STRING VALUE
14}

Usage

If you are using a @azure/msal-react or @azure/msal-browser on the frontend site and you want to verify your Microsoft access token on your node server.

License

This project is licensed under the MIT License - see the LICENSE file for details.