Skip to content

Conversation

@sephiroth-j
Copy link

... when using ReactiveUserDetailsService without ReactiveUserDetailsPasswordService.

The existing test uses a MapReactiveUserDetailsService that implements ReactiveUserDetailsPasswordService, which does not trigger the error.

fixes gh-17986

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Dec 8, 2025
when using `ReactiveUserDetailsService` without `ReactiveUserDetailsPasswordService`

fixes spring-projectsgh-17986

Signed-off-by: Ronny Perinke <23166289+sephiroth-j@users.noreply.github.com>
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.

userDetailsPasswordService cannot be null error when using ReactiveUserDetailsService

3 participants