- Managing issued tokens granted by each user (obtaining a list of clients, and updating scopes and revoking permissions for a particular client)
- Authlete's policy on sweeping unused tokens
- How to specify token(s) on updating its information
- Token duration per scope
- Changing token duration
- How to calculate token duration
- Access Tokens
- Refresh Tokens
- Changing signing key for ID token
- Detecting "claims" expected to be included into ID token
- Generating encrypted ID token
- Adding claims to an ID token
- PKCE (RFC 7636)
- Client Management
- Authorization Endpoint
- User Authentication
- Error Handling
- Client Authentication
- Userinfo Endpoint
Changing signing key for ID token
This article explains an example on changing a signing key for ID token. In order to have Authlete to sign an ID token with the new key, you may have to configure both a service of Authlete and a client registered to the service.
Register a JWK set document to "JWK Set Content" section in Service Settings. See the following article for instructions.
After the registration, add the value of "kid" of this keypair set ("1" in this example) to "ID Token Signature Key ID" section in the same "JWK Set" tab.
In order for the Authlete service to issue an ID token signed with the new key (signature algorithm: ES256), choose "ES256" on "ID Token Signature Algorithm" section in Client Settings.
With the settings above, Authlete will be using the ES256 key (identified by "kid=1") to sign ID tokens for the client.
How did we do with this article?