DevelopmentD.60370 (Customer) asked a question.
I have created an Application on Okta for SAML SSO. Single Login is working as expected. I am using https://github.com/aacotroneo/laravel-saml2 package for the SAML2 part.
This is my SAML Logout Request XML sent to Okta using HTTP Redirect binding.
``` <samlp:LogoutRequest
xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"
ID="ONELOGIN_cc6ef6a1640d109e7ee3de6b78aa88eae9baa2c0"
Version="2.0"
IssueInstant="2021-12-08T07:39:36Z"
Destination="https://dev-82832681.okta.com/app/dev-82832681_schemaapp_1/exk2pl7q1uDDYbCXc5d7/slo/saml">
<saml:Issuer>http://appdev.schemaapp.test/saml2/Slickdeals/metadata</saml:Issuer>
<saml:NameID>ONELOGIN_dbea105d20382e5799161d0fca5221d6c51d4b28</saml:NameID>
<samlp:SessionIndex>id95472156415414861341815572</samlp:SessionIndex>
</samlp:LogoutRequest>```
This seems fine as per documentation and example. But in Okta side, I see this:
What am i missing here? The certificates and keys are configured properly too.
Hello @DevelopmentD.60370 (Customer),
Single Logout (SLO) is a feature in federated authentication where end users can sign out of both their Okta session and a configured application with a single action.
Okta supports this sign-out process only when initiated by a Service Provider (SP). The SP sends the SLO request to Okta to end the Okta session.
You can learn more about this topic using the following link:
https://help.okta.com/en/prod/Content/Topics/Apps/Apps_Single_Logout.htm
Also, feel free to post this question on our Okta Developer Forums: https://devforum.okta.com,
and they should be able to help you with this.
Regards,
Natalia
Okta Inc.