Description
JSON Web Token
Access token
Access tokens are used to inform an API that the bearer of the token has been authorized to access the API and perform a predetermined set of actions specified by the scope. It is used to authorize API access.
The token is generated after a user successfully authenticates and authorizes access.
It does not contain any information about the user itself besides their ID (sub).
It only contains authorization information about which actions the application is allowed to perform at the API (scope).
This is what makes it useful for securing an API, but not for authenticating a user.
An access token is put in the Authorization header of your request, then the API verifies the token and grant access regarding the scope.
| token key
|
description
|
| sub |
user id
|
| scope |
list of authorized accesses
|
ID token
OpenID Connect always issues ID tokens along with access tokens to provide compatibility with OAuth.
ID token carries personal information about end-users that authenticate on an OpenID Connect flow.
| token key
|
description
|
| aud |
Audience: a specific application that should consume the token
|
Content token
| acr |
Authentication Context class Reference |
0 : l'authentification ne respecte pas la norme ISO/IEC 29115
|
| aio |
|
|
| amr |
Authentication Method |
pwd
|
| appid |
APPlication ID |
Application ID dans Azure AD Applications
|
| appidacr |
APPlication Authentication Context class Reference |
- 0 : client publique
- 1 : si le client ID et le client secret sont utilisés
|
| deviceid |
|
|
| oid |
Object ID |
ID unique de l'utilisateur
|
| onprem_sid |
|
|
| scp |
Scope |
user_impersonation
|
| sub |
Subject |
autre ID unique de l'utilisateur
|
| tid |
Tenant ID |
|
| uti |
|
|
