IDP should autogenerate certificate and secret #3909
Labels
Category:Enhancement
Add new functionality
Priority:p2-high
Escalation, on top of current planning, release blocker
Topic:good-first-issue
Is your feature request related to a problem? Please describe.
The IDP autogenerates a certificate and secret inmemory to sign sessions. This means a restart yields a new certificate and secret and therefore invalidates all sessions.
Describe the solution you'd like
The IDP should autogenerate and persist the certificate and secret on disk by default.
Describe alternatives you've considered
You can generate a certificate and a secret manually, so that your sessions survive a restart:
Then you need to configure the IDP to use them:
Additional context
Having the certificate on disk can also prevent a split-brain situation, if you deploy oCIS on two servers. If they share the same data volume (eg. NFS share), they just use the same certificate and secret. If the have it in memory they create sessions only valid for themselves, which is fatal in round robin load balanced situations.
The text was updated successfully, but these errors were encountered: