Repository navigation
dbeaver/pro#11347 Expose verified SSO access claims - #29
Merged
alexander-skoblikov merged 1 commit intoNov 2, 2026
Merged
Conversation
alexander-skoblikov
approved these changes
Nov 2, 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
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.
Account's private access-context endpoint resolves permissions for tokens targeting different resources. Previously it parsed an unverified audience before calling the verifier with that same audience.
Add
verifyAccessToken(token)to return the verified access identity, including its audience, so consumers can enforce the expected resource at the call site. KeepverifyAccessToken(token, expectedAudience)for existing callers. MakeverifiedClaims()public with a sanitizedDDSsoClientException; callers of that lower-level method must validate token purpose and audience. Signature, issuer, timestamps, access-token purpose and strict single-audience validation remain enforced by the access-token verifier.Required by https://github.com/dbeaver/datadam/pull/185; merge and publish this API change before the dependent Account change.
Validation: 664 targeted reactor tests passed with the companion Account changes, including signed-token rejection cases and PostgreSQL Account integration tests. Tests cover audience extraction, malformed/missing/multiple audiences, token purpose, signature, issuer and expiry.
git diff --checkpassed.Related to dbeaver/pro#11347.