Bug 40555 – After UMC logout SSO sessions are still valid on other UMC servers

Bug 40555 - After UMC logout SSO sessions are still valid on other UMC servers


Summary:	After UMC logout SSO sessions are still valid on other UMC servers

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	SAML
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-02-01 16:06 CET by Erik Damrose
Modified:	2021-02-11 17:58 CET (History)
CC List:	2 users (show)

See Also:	51191
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Erik Damrose

2016-02-01 16:06:23 CET

Logging out of one UMC with an SSO session does not invalidate sessions on other UCS UMC servers.

To reproduce, from Bug #39815:
Login to http://master/umc -> single sign-on on
Switch to backup from UMC dropdown on master
Logout on Backup -> redirect to master and backup (for logout)
Enter http://master/umc in browser -> Get a valid UMC Session! Users can be created!

By using SSO i expect to be able to use the 'service' UMC: within the SSO session i can switch to UMCs of different servers, but i am still using the service UMC. If i logout at one endpoint, i expect that every UMC is not accessible for me anymore.

Think of another example: If i log into googlemail i can switch to the calendar, use google drive, docs, etc... If i logout at any of there services  i can not use the others unless i login again. I do not want to logout at every specific service i used.

Counter argument from Bug #39815:
No, this are 2 kinds of sessions. You are not anymore logged in at the IDP. But if you logout at the SP-UMC-1 then I wouldn't logout/destroy the running session at SP-UMC-2. If this would be done and one currently installs e.g. a app on SP-UMC-1 the AppCenter module process would be killed resulting in a maybe broken package state. Therefore I won't change this. The session will be destroyed after the session-timeout of 10 minutes.

Comment 1 Stefan Gohmann

2019-01-03 07:21:52 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.