Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SAML logout issue with Google Workspace #404

Open
atantot opened this issue Dec 8, 2023 · 0 comments
Open

SAML logout issue with Google Workspace #404

atantot opened this issue Dec 8, 2023 · 0 comments

Comments

@atantot
Copy link

atantot commented Dec 8, 2023

Hello,

I'm running into an issue when configuring SAML (with Google Workspace) in Jorani. It works fine except the logout which does not seem to have any effect (which could make sense since I didn't manage to configure it).

Versions

  • Jorani 1.0.2
  • PHP 8.2.
  • SAML with Google Workspace

SAML configuration

    'sp' => array(
        'entityId' => base_url() . 'api/metadata',
        'assertionConsumerService' => array(
            'url' => base_url() . 'api/acs',
        ),
        'singleLogoutService' => array(
            'url' => base_url() . 'api/sls',
        ),
        'NameIDFormat' => 'urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress',
    ),
    'idp' => array(
        'entityId' => 'https://accounts.google.com/o/saml2?idpid=xxxxx',
        'singleSignOnService' => array(
            'url' => 'https://accounts.google.com/o/saml2/idp?idpid=xxxxx',
        ),
        'singleLogoutService' => array(
            'url' => '',
        ),
        'x509cert' => 'xxxyyyzzz',
    ),

Current behavior

  1. In Jorani : after logging in, I choose to log out using the upper right button.
  2. When going back to the base url (jorani.mysite.com), it is still logged in and it does not request again to connect using Google Account.

Expected behavior

After logging out of Jorani, I would expect it to request again to connect using Google Account. Should the SAML config file be set up differently? Do you know any way that I could fix this issue or a workaround?

Note

This issue seems similar to this post here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant