<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
0D54z00009KLA2dCAHOkta Classic EngineSingle Sign-OnAnswered2023-06-28T19:08:03.000Z2023-06-14T15:16:49.000Z2023-06-28T19:08:03.000Z
BillR.84692 likes this.
    • BillR.84692 (Customer)

      I wish I had the answer as well. I'm stuck with the same error.

  • NiallM.34104 (Atlas Identity)

    Ah, so Okta is in the picture 🙂 The answer is right there. There will be no specific documentation for Onelogin/Okta integration but it's something I've done a few times and it works fine. Let me go and dig into a previous config and see if I can screenshot it onto here.

     

  • BillR.84692 (Customer)

    My team has encountered the same error with SAML 2.0 integration with OneLogin. We're using Okta service provider initiated flow. From examination of the Okta system log when the error occurs, the recipient does in fact match what is configured for the Entity ID for the OneLogin customer's identity provider configuration in Okta.

  • SamuelP.19985 (Customer)

    We were able to find a fix. In OneLogin, set the “Recipient” URL to the ACS URL found within the IdP settings in Okta.

    • BillR.84692 (Customer)

      Thank you very much @SamuelP.19985 (Customer)​ ! The solution you described worked for our customer's OneLogin SSO to our Okta IdP as well.

This question is closed.
Loading
OneLogin IdP with SAML 2.0