Skip to content

Refine upgradeEncoding condition in DaoAuthenticationProvider#18788

Open
therepanic wants to merge 1 commit intospring-projects:mainfrom
therepanic:gh-18781
Open

Refine upgradeEncoding condition in DaoAuthenticationProvider#18788
therepanic wants to merge 1 commit intospring-projects:mainfrom
therepanic:gh-18781

Conversation

@therepanic
Copy link
Contributor

After adding jspecify support in the module that contains the DaoAuthenticationProvider class, we actually changed the contract logic, which is a good thing, and this commit fixes it.

Closes: gh-18781

After adding jspecify support in the module that contains the
DaoAuthenticationProvider class, we actually changed the contract logic,
which is a good thing, and this commit fixes it.

Closes: spring-projectsgh-18781

Signed-off-by: Andrey Litvitski <andrey1010102008@gmail.com>
Comment on lines -134 to +137
boolean upgradeEncoding = existingEncodedPassword != null && this.userDetailsPasswordService != null
boolean upgradeEncoding = existingEncodedPassword != null
&& !Objects.equals(this.userDetailsPasswordService, UserDetailsPasswordService.NOOP)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this problem, I believe, is directly related to semantics, I assume we don’t need tests for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: waiting-for-triage An issue we've not yet triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refactor: Improve logic rigor for upgradeEncoding in DaoAuthenticationProvider.createSuccessAuthentication

2 participants