Bug 46127 - office.com logout does not work when login was IdP initiated
office.com logout does not work when login was IdP initiated
Status: REOPENED
Product: UCS
Classification: Unclassified
Component: Office 365
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-24 10:00 CET by Erik Damrose
Modified: 2020-07-06 09:04 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.034
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
screenshot: office logout error message (908.62 KB, image/png)
2018-01-24 10:00 CET, Erik Damrose
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2018-01-24 10:00:24 CET
Created attachment 9359 [details]
screenshot: office logout error message

When the session for office.com was started at the office.com loginpage, the logout works fine:
Office.com -> UCS SAML Login -> office.com -> Logout -> Logout successful

When starting at the UCS Portal, the logout fails as in the the attached screenshot. But the session for office.com is invalidated.
UCS Portal -> UCS SAML Login -> office.com -> Logout -> Logout failed

Maybe we send a different logout link in the xml assertion?
Comment 1 Michel Smidt 2018-11-29 13:45:42 CET
Still an issue at a presentation today
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:51:29 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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