You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When a SAML SLO request is sent by the CAS server to nextcloud, the user session isn't killed whereas the request goes well when activating phpCAS logs. We can see the SAML request as intercepted and without problem of configuration as it's not rejected.
To Reproduce
Steps to reproduce the behavior:
Connect to nextcloud with CAS
Do a logout from CAS and wait the log of the SAML logout request on PHPcas
Refresh the nextcloud UI
See that the user is still connected
Software (please complete the following information):
Server-OS: Debian 9
HTTP-Server Version: Apache 2.4.0
PHP-Version: PHP 7.0
phpCAS-Library-Version: phpCAS 1.3.8
ownCloud/Nextcloud Version 18.0.4
user_cas-Version: user_cas 1.8.5
The text was updated successfully, but these errors were encountered:
The NameID with CAS is not provided (or as @NOT_USED@), did you test with a "standard" CAS ? You should use the samlp:SessionIndex to have a mapping with the ST provided at the session init and the session end.
Hi @jgribonvald
I see the problem, the point is: without saving and mapping the CAS SessionIndex to the ownCloud/Nextcloud session in the ownCloud/Nextcloud database, there is no other way to match a CAS-session to an ownCloud/Nextcloud session than the user-/login-name.
@pingou2712’s Pull-request solves this issue, but has major changes in source code, which I can not test at the moment. This is why I hesitate to accept the pull-request. You are still free to use the changes of @pingou2712 and test, if it works for yourself.
Describe the bug
When a SAML SLO request is sent by the CAS server to nextcloud, the user session isn't killed whereas the request goes well when activating phpCAS logs. We can see the SAML request as intercepted and without problem of configuration as it's not rejected.
To Reproduce
Steps to reproduce the behavior:
Software (please complete the following information):
The text was updated successfully, but these errors were encountered: