TimWillemstein2 (Customer) to rsaSFDCadmin (RSA): asked a question.
Implement SAML for environment with multiple Certificate Subject Alternative Names
Hi All,
I'm looking to implement SAML in my IGL environment. My environment has 3 SANs
that can be used to access IGL from different networks within the company.
i.e. users can use these urls based on their location within the network.
<https://idm.com:8443/aveksa/main>
<https://idm-internal.com:8443/aveksa/main>
<https://igl-idm.com:8443/aveksa/main>
In the SAML configuration I can see the following parameter is required:
Since my end users can access IGL from three different url's I can see a
possible issue here. Does anyone have an idea what would happen if a user
accesses my IGL instance from a different url or how to mitigate this issue?
Also the end users using url 1 cannot use url 2 or 3 to access the
environment.
I'm looking to implement SAML in my IGL environment. My environment has 3 SANs
that can be used to access IGL from different networks within the company.
i.e. users can use these urls based on their location within the network.
<https://idm.com:8443/aveksa/main>
<https://idm-internal.com:8443/aveksa/main>
<https://igl-idm.com:8443/aveksa/main>
In the SAML configuration I can see the following parameter is required:
Since my end users can access IGL from three different url's I can see a
possible issue here. Does anyone have an idea what would happen if a user
accesses my IGL instance from a different url or how to mitigate this issue?
Also the end users using url 1 cannot use url 2 or 3 to access the
environment.
Did you consider creating 3 authentication sources in GL for each of the URLs?
How is working currently? Without SSO?