fm5cy (fm5cy) asked a question.
SAML: Difference between SSO Url, Requestable SSO Url, Recipient Url, Destination Url
I'm trying to get multiple service providers to use one Okta application. For example, if user visits service1.com, the SAML assertion is sent to service1.com/security/saml/acs, if user visists service2.com, the SAML assertion is sent to service2.com/security/saml/acs. What should be the values for SSO Url, Requestable SSO Url, Recipient Url, Destination Url?
There is some documentation on the SAML settings here https://help.okta.com/en/prod/Content/Topics/Apps/Apps_App_Integration_Wizard_SAML.htm, but I couldn't quite parse it. Thank you!
Thank you for reaching out to Okta Community, my name is Ovidiu and I'll be handling your case.
Unfortunately this is not possible.
You will have to create different applications for every SP application.
You can find the information needed for SP side by clicking the view setup instructions button under Sign On Settings.
The information that you have to enter when you create the app in Okta is provided by the SP side usually from the metadata file or from the actual SAML configuration with Okta.
Create a SAML integration using AIW | Okta
I hope the above is useful to you.
Thank You,
Ovidiu Mihalache
Technical Support Engineer
Okta Global Customer Care
Thanks @User16003432765503135491 (Vendor Management) !
Is the ACS url referred to in this post talking about something different then? https://support.okta.com/help/s/question/0D51Y000091jSaC/multiple-acs-urls-in-a-sngle-okta-app?language=en_US
I was under the impression that we could keep adding Requestable SSO URLs (eg ACS urls) as we get more service providers, and the service providers would only need to know the metadata url of the Okta application.