fix: clarification about metadata in subordiante statements #26
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
peppelinux
commented
Sep 19, 2024
peppelinux
temporarily deployed
to
github-pages
GitHub Actions
Inactive
selfissued
approved these changes
Sep 21, 2024
peppelinux
commented
Sep 30, 2024
peppelinux
temporarily deployed
to
github-pages
GitHub Actions
Inactive
selfissued
reviewed
Sep 30, 2024
selfissued
approved these changes
Sep 30, 2024
Co-authored-by: Michael B. Jones <[email protected]>
peppelinux
temporarily deployed
to
github-pages
GitHub Actions
Inactive
peppelinux
commented
Sep 30, 2024
openid-federation-wallet-1_0.md
Outdated
| @@ -421,7 +421,7 @@ These modifications allow a federation authority, such as a Trust Anchor, to app | |||
|
|
|||
| The key difference between `metadata` and `metadata_policy` is that metadata directly affects only the Immediate Subordinate Entity, while `metadata_policy` impacts the configuration of all Subordinate Entities along a Trust Chain, as defined in Sections 5 and 6.1 of [@!OpenID.Federation]. | |||
|
|
|||
| This distinction positions the `metadata` parameter as an ideal tool for federation authorities managing entity registrations and needing to sanitize Leaves configurations in an arbitrary way. The Trust Anchor (TA) and Intermediate (INT) sanitize an Entity Configuration during technical tests and finalize it by setting specific metadata parameters. | |||
| The `metadata` parameter allows federation authorities managing Immediate Subordinates' registrations to sanitize their configurations in an arbitrary way, without necessarily using the policy language in the `metadata_policy` parameter. The Trust Anchor (TA) and Intermediate (INT) sanitize an Entity Configuration and finalize it by setting specific metadata parameters. The `metadata` parameter value updates all the matching parts of the `metadata` JSON object contained within the Subordinate Entity Configuration. | |||
There was a problem hiding this comment.
The `metadata` parameter value updates all the matching parts of the `metadata` JSON object
@selfissued we should say here that it updated if any matching, otherwise it add the unmatching parameters.
selfissued
reviewed
Oct 1, 2024
Co-authored-by: Michael B. Jones <[email protected]>
peppelinux
temporarily deployed
to
github-pages
GitHub Actions
Inactive
peppelinux
commented
Oct 2, 2024
peppelinux
temporarily deployed
to
github-pages
GitHub Actions
Inactive
selfissued
approved these changes
Oct 2, 2024
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.
This PR adds an additional details about applying metadata parameters to immediate subordinates using subordinate statements