Bug 52442 - Store SAML identities in a BDB database
Store SAML identities in a BDB database
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.4
Other Linux
: P5 normal (vote)
: UCS 4.4-7-errata
Assigned To: Florian Best
Jürn Brodersen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-11-30 12:27 CET by Florian Best
Modified: 2020-12-16 16:03 CET (History)
1 user (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): Large environments, UCS Performance
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2020-11-30 12:27:45 CET
The UMC SAML service provider implementation uses pysaml2 which is capable to store SAML identities in a local BDB database instead of in-memory.

We should (optionally?) use this feature to reduce memory usage.
Comment 1 Florian Best univentionstaff 2020-12-01 14:50:28 CET
univention-management-console.yaml
548722752eab | YAML Bug #52371, Bug #52443, Bug #52442, Bug #52444, Bug #52293, Bug #52272

univention-management-console (11.0.5-24)
b00dadc0fdff | Bug #52442: store SAML identities in BDB database
Comment 2 Jürn Brodersen univentionstaff 2020-12-10 00:16:04 CET
What I tested:
Upgrade -> OK
Login -> OK
Login SAML -> OK
users/user -> OK
portal login -> OK
portal edit -> OK
jenkins -> OK
Sessions are now stored in a db on disk -> OK
Merge 5.0 -> OK
YAML -> OK