SAML SP-initiated Single Logout (SLO) is not invalidating sessions prior to redirecting to the IdP #4355

New Issue

OVERLORD · 2026-02-05T08:38:55+03:00

OVERLORD commented

2026-02-05 08:38:55 +03:00

Originally created by @akkornel on GitHub (Dec 6, 2023).

Describe the Bug

Hello! I'd like to report an issue with SAML Logout: When initiating a logout from within Bookstack, Bookstack is not invalidating its session before sending the user to the SAML Identity Provider (IdP).

SAML Logout can work in a couple of different ways:

The logout can be initiated from outside of Bookstack. In this case, the SAML 2.0 IdP (Identity Provider) sends a request to Bookstack, asking for the user to be logged out. This is IdP-initiated Single Logout (SLO).
The logout can be initiated from inside of Bookstack. In this case, Bookstack needs to invalidate its session, and then redirect the user to the IdP to continue the logout process. This is SP-initiated Single Logout (SLO).

I'm reporting a problem the the second method, SP-initiated SLO.

Steps to Reproduce

Configure Bookstack for SAML 2.0 authentication, using an IdP that supports Single Logout (SLO).
Go to the Bookstack main page, and log in to Bookstack via SAML. You are eventually redirected back to Bookstack, and you are logged in.
From within Bookstack, select the "Logout" option. You are redirected to the SAML IdP.
Go back to the Bookstack main page.

Expected Behaviour

I expected to be prompted to log in to Bookstack. Instead, I was presented with the Bookstack main page; my Bookstack session was still valid.

Screenshots or Additional Context

I apologize in advance: This is a messy issue, with a lot of moving parts. If any part of my report is confusing, please let me know!

In the SAML V2.0 Technical Overview, SAML 2.0 Logout is defined in Section 5.3. Section 5.3.2 has a good diagram, showing both IdP-initiated and SP-initiated SLO.

In the diagram, Service Provider sp1.example.com is going through SP-initiated SLO: The user (or, really, their web browser) has asked for a logout (Step 1), and the Service Provider (Bookstack) is redirecting the user to the IdP (Step 2). The redirect is working fine.

What's missing is the session invalidation, as described in the text below the diagram:

The SP sp1.example.com destroys the local authentication session state for the user and then sends the idp.example.org identity provider a SAML <LogoutRequest> message…

The emphasized text is what I'm talking about: In case something goes wrong with the logout process (for example, maybe the IdP is down), the session (on the Bookstack side) should be "destroyed". That being said, Steps 5 and 6 make this more complicated:

The identity provider returns a <LogoutResponse> message containing a suitable status code response to the original requesting service provider, sp1.example.com [Bookstack]. The response is digitally signed and returned (in this case) using the HTTP Redirect binding

Finally, the service provider sp1.example.com [Bookstack] informs the user that they are logged out of all the providers.

The reason I say this is confusing is because, even though the authentication session state is supposed to be destroyed in Step 1, the SP (Bookstack) is still supposed to store enough information to be able to authenticate the message from the IdP in Step 5, and do something with the user in Step 6 (which I think, for Bookstack, is to return the user to the main page).

I understand that you're using php-saml, and looking through their documentation, I see there isn't any mention of the need to destroy local authentication session state (Step 1 from the top of this section). I'm wondering if there should also be an Issue raised with the php-saml folks.

Browser Details

No response

Exact BookStack Version

23.10.4

Originally created by @akkornel on GitHub (Dec 6, 2023). ### Describe the Bug Hello! I'd like to report an issue with SAML Logout: When initiating a logout from within Bookstack, Bookstack is not invalidating its session before sending the user to the SAML Identity Provider (IdP). SAML Logout can work in a couple of different ways: 1. The logout can be initiated from outside of Bookstack. In this case, the SAML 2.0 IdP (Identity Provider) sends a request to Bookstack, asking for the user to be logged out. This is IdP-initiated Single Logout (SLO). 2. The logout can be initiated from inside of Bookstack. In this case, Bookstack needs to invalidate its session, and then redirect the user to the IdP to continue the logout process. This is SP-initiated Single Logout (SLO). I'm reporting a problem the the second method, SP-initiated SLO. ### Steps to Reproduce 1. Configure Bookstack for SAML 2.0 authentication, using an IdP that supports Single Logout (SLO). 2. Go to the Bookstack main page, and log in to Bookstack via SAML. You are eventually redirected back to Bookstack, and you are logged in. 3. From within Bookstack, select the "Logout" option. You are redirected to the SAML IdP. 4. Go back to the Bookstack main page. ### Expected Behaviour I expected to be prompted to log in to Bookstack. Instead, I was presented with the Bookstack main page; my Bookstack session was still valid. ### Screenshots or Additional Context I apologize in advance: This is a messy issue, with a lot of moving parts. If any part of my report is confusing, please let me know! In the [SAML V2.0 Technical Overview](http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0-cd-02.html), SAML 2.0 Logout is defined in [Section 5.3](http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0-cd-02.html#5.3.Single%20Logout%20Profile|outline). [Section 5.3.2](http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0-cd-02.html#5.3.2.SP-Initiated%20Single%20Logout%20with%20Multiple%20SPs|outline) has a good diagram, showing both IdP-initiated and SP-initiated SLO. In the diagram, Service Provider `sp1.example.com` is going through SP-initiated SLO: The user (or, really, their web browser) has asked for a logout (Step 1), and the Service Provider (Bookstack) is redirecting the user to the IdP (Step 2). The redirect is working fine. What's missing is the session invalidation, as described in the text below the diagram: > 2. The SP sp1.example.com _destroys the local authentication session state_ for the user and then sends the idp.example.org identity provider a SAML `<LogoutRequest>` message… The _emphasized text_ is what I'm talking about: In case something goes wrong with the logout process (for example, maybe the IdP is down), the session (on the Bookstack side) should be "destroyed". That being said, Steps 5 and 6 make this more complicated: > 5. The identity provider returns a `<LogoutResponse>` message containing a suitable status code response to the original requesting service provider, sp1.example.com [Bookstack]. The response is digitally signed and returned (in this case) using the HTTP Redirect binding > 6. Finally, the service provider sp1.example.com [Bookstack] informs the user that they are logged out of all the providers. The reason I say this is confusing is because, even though the authentication session state is supposed to be destroyed in Step 1, the SP (Bookstack) is still supposed to store enough information to be able to authenticate the message from the IdP in Step 5, and do something with the user in Step 6 (which I think, for Bookstack, is to return the user to the main page). I understand that you're using [php-saml](https://github.com/SAML-Toolkits/php-saml), and looking through their documentation, I see there isn't any mention of the need to destroy local authentication session state (Step 1 from the top of this section). I'm wondering if there should also be an Issue raised with the php-saml folks. ### Browser Details _No response_ ### Exact BookStack Version 23.10.4

OVERLORD added the 🐛 Bug 🚪 Authentication labels 2026-02-05 08:38:55 +03:00

OVERLORD closed this issue

2026-02-05 08:38:56 +03:00

OVERLORD commented

2026-02-05 08:38:58 +03:00

@ssddanbrown commented on GitHub (Dec 6, 2023):

Thanks for raising @akkornel, I agree this is currently not as per spec. I get the feeling I misunderstood the point of logout, by step 6 of the diagram specifically labelled as "Logged out" between the SP and browser.

I'll assign this to be addressed for the next BookStack feature release.
Thanks for the effort of the detailed explanation given in this issue.

@ssddanbrown commented on GitHub (Dec 6, 2023): Thanks for raising @akkornel, I agree this is currently not as per spec. I get the feeling I misunderstood the point of logout, by step 6 of the diagram specifically labelled as "Logged out" between the SP and browser. I'll assign this to be addressed for the next BookStack feature release. Thanks for the effort of the detailed explanation given in this issue.

OVERLORD commented

2026-02-05 08:39:03 +03:00

@radiantwave commented on GitHub (Dec 7, 2023):

#2553 related?

Have the same issue right now.
This is pretty drastic for me, since users can't change accounts at all.
Authenticating with another user doesn't log you into the desired account because the old sessions never end.

@radiantwave commented on GitHub (Dec 7, 2023): #2553 related? Have the same issue right now. This is pretty drastic for me, since users can't change accounts at all. Authenticating with another user doesn't log you into the desired account because the old sessions never end.

OVERLORD commented

2026-02-05 08:39:07 +03:00

@ssddanbrown commented on GitHub (Dec 7, 2023):

@radiantwave Related, but not the same. In a full logout flow you should be returned to BookStack eventually where you'll then be logged out of BookStack. This is the wrong point of logout within BookStack, which is what this issue addresses, but logout should work in most cases unless cancelled (or something goes wrong) on the IdP side of things.

#2553 was maybe more similar to your issue but likely specific to meeting Azure's requirements.
Your issue is likely similar, but specific to your IdP, although it would also be solved by this issue once addressed (although that would still leave a question if why you're not reaching the latter parts of the flow).

@ssddanbrown commented on GitHub (Dec 7, 2023): @radiantwave Related, but not the same. In a full logout flow you should be returned to BookStack eventually where you'll then be logged out of BookStack. This is the wrong point of logout within BookStack, which is what this issue addresses, but logout should work in most cases unless cancelled (or something goes wrong) on the IdP side of things. #2553 was maybe more similar to your issue but likely specific to meeting Azure's requirements. Your issue is likely similar, but specific to your IdP, although it would also be solved by this issue once addressed (although that would still leave a question if why you're not reaching the latter parts of the flow).

OVERLORD commented

2026-02-05 08:39:08 +03:00

@ssddanbrown commented on GitHub (Dec 8, 2023):

This has now been addressed via 8cbaa3e27c, with testing added and manual testing performed via Keycloak, via both SP and IdP initiated logout, with various configuration changes and forced breaking of the full auth flow.

These changes will be part of the next feature release.
Thanks again @akkornel for raising.

@ssddanbrown commented on GitHub (Dec 8, 2023): This has now been addressed via 8cbaa3e27c7eb038f010638d3b4b91f3a1a5a644, with testing added and manual testing performed via Keycloak, via both SP and IdP initiated logout, with various configuration changes and forced breaking of the full auth flow. These changes will be part of the next feature release. Thanks again @akkornel for raising.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#4355