<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007VhE8ACAVOkta Classic EngineSingle Sign-OnAnswered2022-03-16T16:49:16.000Z2022-03-15T12:48:31.000Z2022-03-16T16:49:15.000Z

AndrewZ.07293 (Customer) asked a question.

ACS URL in an IDP-initiated login scenario

I've been struggling to understand how to use one app integration for multiple domains using SAML, which in my mind would be the whole point of SSO. Is there a way to specify Requestable SSO URLs for an IDP-initiated login?

 

I am hitting the Identity Provider Single Sign-On URL, which is something like https://{domain}.okta.com/app/{app}/{app_id}/sso/saml, but I can't find a way to instruct Okta to return to my preferred POST-back url. I configured multiple ACS URLs and need a way to select them dynamically in the request. Does anyone know how to pass AssertionConsumerServiceURL into this request?

 

For now I have to use one app integration per domain and each app has it's own Single Sign On URL defined for the domain. I don't understand why SP-initiated would have this feature, but IDP initiated not.


This question is closed.
Loading
ACS URL in an IDP-initiated login scenario