-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add fallback routines for empty secret cases #31499
Conversation
Test results when having an instance without a secret and adding one afterwards:
|
Retested with follow up commits:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good and I tested it manually and I didn't get logged when moving from a config without secret to a config.php with a secret
Signed-off-by: Julius Härtl <jus@bitgrid.net>
Signed-off-by: Julius Härtl <jus@bitgrid.net>
Signed-off-by: Julius Härtl <jus@bitgrid.net>
57a7255
to
a6796b4
Compare
Signed-off-by: Carl Schwan <carl@carlschwan.eu>
Should we merge it without the migration path and just add the warning from #31492 instead? It's better than the current state |
Co-authored-by: Joas Schilling <213943+nickvergessen@users.noreply.github.com> Signed-off-by: Carl Schwan <carl@carlschwan.eu>
/backport to stable25 |
Manual backport #35605 |
Make sure to keep authentication working when an instance has been setup without a secret after adding the secret manually afterwards.
Provides a possible migration path for #31492
ToDo