Bug 39455 - On update SAML domain sso is not set up correctly when SAML App was installed
On update SAML domain sso is not set up correctly when SAML App was installed
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: SAML
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1
Assigned To: Erik Damrose
Stefan Gohmann
: interim-2
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-02 10:39 CEST by Erik Damrose
Modified: 2015-11-17 12:12 CET (History)
2 users (show)

See Also:
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

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2015-10-02 10:39:28 CEST
When updating to UCS 4.1 and the SAML App was installed, the domain SSO is not set up correctly.

The join scripts currently do not overwrite the UCR variables with the ucs-sso.$domainname setting and no new certificate will be generated.

We can not simply overwrite these settings, that would break the old SAML configuration one had with service providers.
Comment 1 Erik Damrose univentionstaff 2015-10-28 16:57:00 CET
Unset certificate UCRVs in univention-saml.postinst leads to default UCS SAML setup. No update path available, as we require new certificates from the ucsCA. 
A note was added to the release notes.

r64944 univention-saml 3.0.25-2.88.201510281614
r64946 release notes
Comment 2 Stefan Gohmann univentionstaff 2015-11-03 12:23:57 CET
Yes it works like expected.
Comment 3 Stefan Gohmann univentionstaff 2015-11-17 12:12:06 CET
UCS 4.1 has been released:
 https://docs.software-univention.de/release-notes-4.1-0-en.html
 https://docs.software-univention.de/release-notes-4.1-0-de.html

If this error occurs again, please use "Clone This Bug".