Which is the application ID of the client using the token?
The application ID of the client using the token. The application can act as itself or on behalf of a user. The application ID typically represents an application object, but it can also represent a service principal object in Azure AD. Only present in v2.0 tokens, a replacement for appid. The application ID of the client using the token.
Can a resource accept a Microsoft identity token?
Resources accept the token. The Microsoft identity platform supports issuing any token version from any version endpoint – they are not related. This is why a resource setting accessTokenAcceptedVersion to 2 means that a client calling the v1.0 endpoint to get a token for that API will receive a v2.0 access token.
Who are the parties involved in an access token request?
There are two parties involved in an access token request: the client, who requests the token, and the resource (the API) that accepts the token when the API is called. The aud claim in a token indicates the resource the token is intended for (its audience ).
Which is an example of an access token validation?
Examples include pwd_exp (not every tenant requires passwords to expire) and family_name ( client credential flows are on behalf of applications which don’t have names). Claims used for access token validation will always be present. Some claims are used to help Azure AD secure tokens in case of reuse.
What are the different versions of access tokens?
There are two versions of access tokens available in the Microsoft identity platform: v1.0 and v2.0. These versions govern what claims are in the token, ensuring that a web API can control what their tokens look like.
How to validate Microsoft identity platform access tokens?
Validating tokens. To validate an id_token or an access_token, your app should validate both the token’s signature and the claims. To validate access tokens, your app should also validate the issuer, the audience, and the signing tokens. These need to be validated against the values in the OpenID discovery document.