feat: RPI Architectures and Implementation Scenarios documentation #31
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
This document proposes three implementation scenarios for Relying Party solutions relying on third party solution (interop gateway/proxy), where only on them appears fully compliant to the profile of RP Intermediary (RPI) as defined in ETSI TS 119 612 and the eIDAS 2.0 regulation. This PR aims to includes detailed requirements, architecture, and sequence diagrams for each scenario. Each of this scenario aims to propose implementation experiences based on real world use case.
Clarified compliance details for RPI scenarios and updated examples.
peppelinux
requested review from
RosaliaGaleano,
Saramandus,
elisanp,
sander,
slistrom and
thodoris
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 document proposes three implementation scenarios for Relying Party solutions relying on a third party solution (interop gateway/proxy), where only one of them appears fully compliant to the profile of RP Intermediary (RPI) as defined in ETSI TS 119 612 and the eIDAS 2.0 regulation.
This PR aims to include detailed requirements, architecture, and sequence diagrams for each scenario. Each of this scenario aims to propose implementation experiences based on real world use case.
Too properly see the sequence diagram please read the file the "View file" function, as shown below.