-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
fix: Do not build encrypted password if there is none #51130
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
Conversation
|
/backport to stable31 |
|
/backport to stable28 |
|
/backport to stable29 |
|
/backport to stable30 |
provokateurin
left a comment
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.
Sounds like something that requires a test to avoid regressions.
pabzm
left a comment
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.
Apart from the minor style suggestion it looks good to me! 👍
Signed-off-by: Julius Knorr <[email protected]>
666a017 to
777cd94
Compare
|
Pushed a unit test |
This fixes a regression from #48915 where user backends without passwords would store an encrypted empty password for new app passwords.
While they first work, after 5 minutes the password is checked and cannot be validated as there is none so the token expired.
Checklist