Hi there,
I’m investigating a flow where the original SAML AuthnRequest is generated and tracked outside of ComponentSpace.
We currently have long-established IdP-initiated and a more recent SP-initiated SAML flows working with ComponentSpace 6.3 - High-Level API
We’re now investigating a new mobile authentication flow where the SAML AuthnRequest is generated and tracked by a mobile middleware by a third-party dev team, rather than our application
Their proposed solution is:
- The mobile middleware generates the AuthnRequest and sends the user to the IdP.
- The IdP authenticates the user.
- The SAML Response is posted to an ACS implemented using ComponentSpace in our application.
- After validating the SAML Response, user, etc our application reads the InResponseTo value and passes it back to the mobile middleware for request correlation.
A few questions:
- Can ComponentSpace validate a SAML Response when the original AuthnRequest was not generated or tracked by ComponentSpace?
- Is DisableInResponseToCheck the correct setting for this scenario?
- If enabled, which validations remain in place?
- After successful validation, what is the recommended way to obtain a trusted InResponseTo value?
- Are there any security concerns or recommended practices for this approach.
Cheers, Patrick