[Security] Support new sap_id_typeclaim#1124
Merged
CharlesDuboisSAP merged 2 commits intomainfrom Mar 18, 2026
Merged
Conversation
strehle
approved these changes
Mar 17, 2026
Member
|
@torsten-sap FYI |
newtork
approved these changes
Mar 18, 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.
Context
New for SCI is now a
sap_id_typeclaim. This claim is always in the JWT (id and access token).With value
appyou can rely on a client authentication only and thesubis then always theclient_id.With value
useryou can rely on a User authentication and then you can rely thatsubis the user identifier. This Identifier is called Subject Name Identifier in SCI and in the Admin UI customers can define this. Typically theuserId, oremailoruser_uuid.Feature scope:
sap_id_typeclaimDefinition of Done
Documentation updated