SAML Single Logout is not working properly due to incomplete LogoutRequest XML

CMS Version



I am now trying to use single sign-on and single logout via ADFS in my Xibo cms.
I have successfully connect Xibo cms and ADFS for the SSO part.
However, for SLO, the ADFS did not provide a logout response with status:Success, but a status:Requester instead.



# If you need to add custom configuration settings to the CMS settings.php file,
# this is the place to do it.

# For example, if you want to configure SAML authentication, you can add the
# required configuration here

$authentication = new \Xibo\Middleware\SAMLAuthentication();
$samlSettings = array (
   'workflow' => array(
        // Enable/Disable Just-In-Time provisioning
        'jit' => true,
        // Attribute to identify the user
        'field_to_identify' => 'UserName',   // Alternatives: UserID, UserName or email
        // Default libraryQuota assigned to the created user by JIT
        'libraryQuota' => 1000,
        // Initial User Group
        'group' => 'Users',
        // Home Page
        'homePage' => 'icondashboard.view',
        // Enable/Disable Single Logout
        'slo' => true,
        // Attribute mapping between XIBO-CMS and the IdP
        'mapping' => array (
#            'UserID' => '3',
#            'usertypeid' => '3',
            'UserName' => 'uid',
            'email' => 'mail',
   // Settings for the PHP-SAML toolkit.
   // See documentation:
   'strict' => false,
   'debug' => true,
   'idp' => array (
            'entityId' => '',
            'singleSignOnService' => array (
                'url' => '',
            'singleLogoutService' => array (
                'url' => '',
            'x509cert' => 'MIIC...',
   'sp' => array (
        'entityId' => '',
        'assertionConsumerService' => array (
            'url' => '',
        'singleLogoutService' => array (
            'url' => '',
        'NameIDFormat' => 'urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress',
        'x509cert' => 'MIIG...',
        'privateKey' => 'MIIE...',
    'security' => array (
        'nameIdEncrypted' => false,
        'authnRequestsSigned' => false,
        'logoutRequestSigned' => true,
        'logoutResponseSigned' => false,
        'signMetadata' => false,
        'wantMessagesSigned' => false,
        'wantAssertionsSigned' => false,
        'wantAssertionsEncrypted' => false,
        'wantNameIdEncrypted' => false,



    <saml:NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:entity"></saml:NameID>


<samlp:LogoutResponse ID="_48624035-2d2c-44c3-b4d4-e7d7085301ca" Version="2.0" IssueInstant="2021-07-20T02:11:43.021Z" Destination="" Consent="urn:oasis:names:tc:SAML:2.0:consent:unspecified" InResponseTo="ONELOGIN_80eaf227e7b041f1e85f0406dabaca2fb0c8d452" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
    <Issuer xmlns="urn:oasis:names:tc:SAML:2.0:assertion"></Issuer>
        <samlp:StatusCode Value="urn:oasis:names:tc:SAML:2.0:status:Requester" />

I am wondering the status:Requster is due to some missing fields in the LogoutRequest, as I saw there should be some other fields (eg. sessionIndex nameIdFormat) in some other LogoutRequest examples.
I noticed that there are some differences between xibo cms code and onelogin SAML demo code when calling the logout function. Arguments are not passed to the logout function in Xibo for constructing the LogoutRequest XML. Is this a correct usage of the logout function?
Thanks in advance.



Hi and welcome.

To be honest with you, we’re not sure! Our SAML auth middleware was written originally by the one of the team at onelogin, and we’ve pretty much stuck with their initial implementation since then. It could be that the spec/library have advanced since then.

I’ve got SLO working fine here as-is though, so maybe there are some environment specific option coming into play.

As you have an environment to reproduce the issue, are you able to make the modifications and try it out?


This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.