PietH.37941 (Customer) asked a question.
SAML - HTTP-Redirect instead of HTTP-POST at Single Logout
Hi there! I'm currently building an online php application for which I'm using Okta as Identity Provider. It's a mulit tenant app (tenants are recognized by url (ex. https://server.com/saml/{tenant}/login)). Single Sign On is working just fine, but the fact that Single Logout doesn't work is becoming a big issue. I figured that it's because the library I use (onelogin/php-saml), only supports the HTTP-Redirect binding at SLO, but Okta sends a HTTP-POST response by default. Is there an option so that we Okta uses HTTP-Redirect instead of HTTP-POST? Thanks in advance!- Roban BTW: Here is the error and stacktrace I constantly get: OneLogin_Saml2_Error in Auth.php line 211: SAML LogoutRequest/LogoutResponse not found. Only supported HTTP_REDIRECT Binding in Auth.php line 211 at OneLogin_Saml2_Auth->processSLO(false, null, true, object(Closure)) in Saml2Auth.php line 110 at Saml2Auth->sls(true) in Saml2Controller.php line 87 at Saml2Controller->sls('demo') at call_user_func_array(array(object(Saml2Controller), 'sls'), array('tenant' => 'demo')) in Controller.php line 80 at Controller->callAction('sls', array('tenant' => 'demo')) in ControllerDispatcher.php line 146 at ControllerDispatcher->call(object(Saml2Controller), object(Route), 'sls') in ControllerDispatcher.php line 94 at ControllerDispatcher->Illuminate\Routing\{closure}(object(Request)) at call_user_func(object(Closure), object(Request)) in Pipeline.php line 52 at Pipeline->Illuminate\Routing\{closure}(object(Request)) at call_user_func(object(Closure), object(Request)) in Pipeline.php line 102 at Pipeline->then(object(Closure)) in ControllerDispatcher.php line 96 ...
