Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-20 Thread Indunil Upeksha Rathnayake
Hi, Thanks for all of your ideas. Please note that with this implementation, following extensions in SAML has been introduced for the following reasons. EidasExtensionProcessor - process the SAML extension and retrieve the required attribute list. EidasSAMLAssertionBuilder - validate whether all

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-19 Thread Indunil Upeksha Rathnayake
On Thu, Mar 15, 2018 at 6:55 AM, Harsha Thirimanna wrote: > > > On Mon, 12 Mar 2018, 13:48 Johann Nallathamby, wrote: > >> >> >> On Mon, Mar 12, 2018 at 10:58 AM, Indunil Upeksha Rathnayake < >> indu...@wso2.com> wrote: >> >>> Hi, >>> >>> In order to support

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-14 Thread Harsha Thirimanna
On Mon, 12 Mar 2018, 13:48 Johann Nallathamby, wrote: > > > On Mon, Mar 12, 2018 at 10:58 AM, Indunil Upeksha Rathnayake < > indu...@wso2.com> wrote: > >> Hi, >> >> In order to support eIDAS profile in IS, as per the 4 eIDAS >> specifications in [1], there are a set of

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-12 Thread Johann Nallathamby
On Mon, Mar 12, 2018 at 10:58 AM, Indunil Upeksha Rathnayake < indu...@wso2.com> wrote: > Hi, > > In order to support eIDAS profile in IS, as per the 4 eIDAS specifications > in [1], there are a set of requirements to be considered including message > format, cryptographic requirements etc. Those

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-11 Thread Indunil Upeksha Rathnayake
Hi, In order to support eIDAS profile in IS, as per the 4 eIDAS specifications in [1], there are a set of requirements to be considered including message format, cryptographic requirements etc. Those requirements has been summarized in [2]. This is regarding the handling and inclusion of

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-11 Thread Ruwan Abeykoon
Hi Indunil, Please make sure this behavior is properly explained in the documentation, with references to the spec. Cheers, Ruwan On Mon, Mar 12, 2018 at 10:30 AM, Indunil Upeksha Rathnayake < indu...@wso2.com> wrote: > > > On Wed, Feb 28, 2018 at 5:15 PM, Dulanja Liyanage >

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-03-11 Thread Indunil Upeksha Rathnayake
On Wed, Feb 28, 2018 at 5:15 PM, Dulanja Liyanage wrote: > If extensions are coming in the SAML AuthnRequest from the SP, then, IIRC, > that *same extension* will be copied to the AuthnRequest going to the > Federated IdP. Is that behaviour acceptable for this scenario? Please

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-02-28 Thread Dulanja Liyanage
If extensions are coming in the SAML AuthnRequest from the SP, then, IIRC, that *same extension* will be copied to the AuthnRequest going to the Federated IdP. Is that behaviour acceptable for this scenario? Please validate that. On Wed, Feb 28, 2018 at 7:56 AM, Johann Nallathamby

Re: [Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-02-27 Thread Johann Nallathamby
Hi Indunil, On Tue, Feb 27, 2018 at 3:56 PM, Indunil Upeksha Rathnayake < indu...@wso2.com> wrote: > Hi, > > eIDAS (electronic IDentification, Authentication and trust Services) is an > EU regulation on electronic identification and trust services for > electronic transactions in the internal

[Dev] [Architecture] [IAM] eIDAS profile support for SAML

2018-02-27 Thread Indunil Upeksha Rathnayake
Hi, eIDAS (electronic IDentification, Authentication and trust Services) is an EU regulation on electronic identification and trust services for electronic transactions in the internal market. The eIDAS interoperability framework including its national entities (eIDAS-Connector and eIDAS-Service)