Bug 50804 - Installing an app on a dc master or dc backup causes restart of the saml memcache service
Installing an app on a dc master or dc backup causes restart of the saml memc...
Status: NEW
Product: UCS
Classification: Unclassified
Component: SAML
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-02-07 17:01 CET by Jürn Brodersen
Modified: 2020-03-02 10:39 CET (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 5: Will affect all 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.286
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

Note You need to log in before you can comment on or make changes to this bug.
Description Jürn Brodersen univentionstaff 2020-02-07 17:01:40 CET
Installing an app on a dc master or dc backup causes restart of the saml memcache service

The listener script restart "univention-saml" on any changes to the "univentionService" attribute. This results in saml loosing all sessions (bug 39800)

For example if an administrator is logged in using saml and installs an app he has to log in again after the installation finished.
Comment 1 Christina Scheinig univentionstaff 2020-02-28 13:38:13 CET
Could this be also a problem with the user import module in ucs@school? A customer reported a similar sounding behaviour in that module using saml.
Comment 2 Jürn Brodersen univentionstaff 2020-03-02 10:39:18 CET
(In reply to Christina Scheinig from comment #1)
> Could this be also a problem with the user import module in ucs@school? A
> customer reported a similar sounding behaviour in that module using saml.

I don't think so. The fix from bug 50670 should help.