Fedora Account System
Red Hat Associate
Red Hat Customer
When an administrator revokes existing tokens by raising the realm (or client/user) not-before value, ID tokens issued before that cutoff are still accepted by the UMA grant when they are submitted as a claim token in the ID token format. Keycloak verifies the signature, client and expiration of the ID token but does not enforce the not-before revocation boundary. As long as the user's session is still active, Keycloak builds a new identity from it and issues a fresh Requesting Party Token (RPT) carrying the evaluated authorization permissions. This defeats the administrator's explicit token revocation. The affected endpoint is the token endpoint (POST /realms/{realm}/protocol/openid-connect/token) using the UMA grant (urn:ietf:params:oauth:grant-type:uma-ticket) with claim_token_format set to the ID token format.