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.
I think we need to work on the format - it could of course be posted as a draft report since it's interesting for the consortium but it should also be suggested in the form of ADRs, CS and as part of the blueprint document. Also I am not sure how this relates to the work done in #37 (if it does at all :) ).
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.
I think we need to work on the format - it could of course be posted as a draft report since it's interesting for the consortium but it should also be suggested in the form of ADRs, CS and as part of the blueprint document. Also I am not sure how this relates to the work done in #37 (if it does at all :) ).