Add revocation_endpoint to OpenID Connect discovery document#1058
Merged
vharseko merged 2 commits intoJun 21, 2026
Merged
Conversation
maximthomas
approved these changes
Jun 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This pull request adds the revocation_endpoint metadata to the OpenID Connect Discovery document (/.well-known/openid-configuration).
The token revocation endpoint is already implemented by OpenAM (/oauth2/revoke), but it is not advertised in the OpenID Connect discovery document.
Changes
Added getRevocationEndpoint() to OAuth2Uris.
Implemented the endpoint in OAuth2UrisFactory.OAuth2UrisImpl.
Added the revocation_endpoint property to OpenIDConnectProviderConfiguration.
Example
Before:
{
"token_endpoint": "https://server/oauth2/access_token"
}
After:
{
"token_endpoint": "https://server/oauth2/access_token",
"revocation_endpoint": "https://server/oauth2/revoke"
}
Compatibility
This change is fully backward compatible, as it only adds an additional metadata field to the discovery document and does not modify any existing endpoint behavior.
This endpoint is defined by RFC 7009 and can be advertised through the authorization server metadata used by OpenID Connect Discovery.