Feat/1295 move saml config to db #1349
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
February 16, 2024 14:01
* add missing error logging as there is no real error output when there is a internal server error * switch parseSamlResponse errors to invalid request errors. Fixes: #1254
* 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
* 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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds the possibility to save saml provider configurations in database.
Implementation