Create eid-federation-api.yaml #65
Draft
Conversation
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
1 participant
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.
The technologies and protocols currently used in digital identity federations are SAML2 and OIDC. In the future these protocols could be replaced by others, as a consequent technological and infrastructural evolution of the Federations of Digital Identities. For this reason, this document specifies a scheme that can be extended over time and based on Open API, conforming to the national interoperability model.
This scheme unifies draft-young-md-query (MDQ) and OIDC Federation 1.0 resources for the National Federation Authority role.
It wants to achieve the result of maintaining a backward compatibility with the pre-existing SAML2 entities and at the same time introducing the innovations of OIDC Federation 1.0.