An explicit client registration may contain metadata for more than one entity_type. #191
Conversation
This file contains 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
…e entity_type. The metadata for each type in the registration response must be verified.
peppelinux
reviewed
Mar 19, 2025
selfissued
reviewed
Mar 24, 2025
Punctuation
selfissued
approved these changes
Mar 24, 2025
peppelinux
approved these changes
Mar 25, 2025
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.
Apart from the fact that the set of entity type in the request response MUST be the same as in the request the metadata for each type in the response must be validated against the metadata policies in a trust chain collected based on the response claims trust_anchor_id and authority_hints.