First Last Prev Next    This bug is not in your last search results.
Bug 55395 - Automatically register UMC (/univention/saml/) as a client for each UCS system
Automatically register UMC (/univention/saml/) as a client for each UCS system
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: Keycloak
UCS 5.0
Other Linux
: P5 normal (vote)
: UCS 5.0-2-errata
Assigned To: Nikola Radovanovic
Julia Bremer
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2022-11-08 10:04 CET by Nikola Radovanovic
Modified: 2022-12-14 15:04 CET (History)
2 users (show)

See Also:
What kind of report is it?: Development Internal
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.
Comment 1 Nikola Radovanovic univentionstaff 2022-11-08 10:31:50 CET 
When the Administrator chooses to set Keycloak as the primary SSO IdP/OP, the Portal/UMC of every (current and future!) UCS should be configured automatically to use Keycloak.
Comment 2 Nikola Radovanovic univentionstaff 2022-12-09 13:05:29 CET 
0e20098337 | Register UMC as a Keycloak client, but ignore failure
18ba879d3f | Advisory
Comment 3 Julia Bremer univentionstaff 2022-12-11 22:26:15 CET 
OK: Package built
~OK: UMC SAML client registration - UMC needs a "special" uid mapper for SAML (fixed in 9d6ac79a1daa69) 
OK: Errors are ignored
OK: Yaml

Verified
First Last Prev Next    This bug is not in your last search results.