Skip to content

Conversation

@juliusknorr
Copy link
Member

@juliusknorr juliusknorr commented Dec 10, 2022

Summary

Otherwise restoring the requesttoken would reopen and read the existing
session data and restore it instead of clearing.

This is only an issue if the session clean method is called without having a
session already open (e.g. with the @UseSession controller annotation. This
is the reason why the regular logout works but user_saml not.

There is a hot fix available for user_saml in nextcloud/user_saml#677 so this could be addressed without another server release.

Signed-off-by: Julius Härtl jus@bitgrid.net

Checklist

Otherwise restoring the requesttoken would reopen and read the existing
session data and restore it instead of clearing

Signed-off-by: Julius Härtl <jus@bitgrid.net>
@juliusknorr
Copy link
Member Author

/backport to stable25

Copy link
Member

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 assuming this is still useful, probably for other use cases

@PVince81 PVince81 merged commit 761221b into master Dec 20, 2022
@PVince81 PVince81 deleted the bugfix/35708 branch December 20, 2022 16:25
@backportbot-nextcloud
Copy link

The backport to stable25 failed. Please do this backport manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3. to review Waiting for reviews bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: SAML Logout broken on 25

5 participants