Add SAML config to database #1295
Assignees
Labels
enhancement
New feature or request
Comments
shentschel
pushed a commit
that referenced
this issue
Feb 16, 2024
* add migrations * add database models * create a list of config providers and db providers on every call to be able to dynamically update them in case a new one was saved to the database -> prevents restarting the application Closes: #1295
shentschel
pushed a commit
that referenced
this issue
Feb 16, 2024
* add migrations * add database models * create a list of config providers and db providers on every call to be able to dynamically update them in case a new one was saved to the database -> prevents restarting the application Closes: #1295
shentschel
pushed a commit
that referenced
this issue
Feb 20, 2024
* add note for checking and debugging attribute fields * add chapter to inform about the possibility to persist SAML providers to database Related to: #1295
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Description
It would be nice to store the SAML Identity providers in the database, because when you deploy Hanko in kubernetes and have many Identity provider you will run into the K8s ConfigMap limit of 1MiB.
We would also need CRUD endpoints in the admin API.
Describe your ideal solution
No response
Workarounds or alternatives
No response
Hanko Version
v0.9.1
Additional Context
No response
The text was updated successfully, but these errors were encountered: