Skip to content

Tighter validation of id_token_hint at endsession endpoint. - #186

Merged
patchandthat merged 4 commits into
mainfrom
bug/id-token-validation
Nov 18, 2026
Merged

patchandthat merged 4 commits into
mainfrom
bug/id-token-validation

Conversation

@patchandthat

Copy link
Copy Markdown
Collaborator

Description

This change ensures that the token passed as id_token_hint at the end session endpoint has its typ validated against an allowlist defined in IdentityServerOptions.IdentityTokenJwtTypes, and ensures the token has a subjectId and that subjectId matches the current subject.

While the introspection weakness in Duende is not present in Open.IdentityServer, as only ApiResources can access the introspection endpoint, the access token from an ApiResource with the same name as a ClientId could be used at the end session endpoint to logout and redirect to that clients post_logout_redirect.

Type of change

  • Bug fix
  • Feature
  • Refactoring
  • Documentation
  • Other

Does this PR introduce a breaking change?

Does the change cause a breaking change to any of the following?

  • Changes to existing public APIs or DB schema
  • Changes which could cause existing behaviour to fail (eg. feature restrictions, changes to default values, stricter validation, etc)

Testing

Additional unit and integration tests added.

LLM Usage

Research and test code.

@patchandthat
patchandthat merged commit 5c9f24a into main Nov 18, 2026
3 checks passed
@patchandthat
patchandthat deleted the bug/id-token-validation branch November 18, 2026 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants