Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Servlet-based UserDetailsServiceAutoConfiguration is active in a reactive app #43334

Conversation

BenchmarkingBuffalo
Copy link
Contributor

The UserDetailsServiceAutoConfiguration is only to be active in a servlet based web application

See gh-43326

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Nov 30, 2024
@BenchmarkingBuffalo BenchmarkingBuffalo force-pushed the 43326-servlet-based-UserDetailsServiceAutoConfiguration-is-active-in-a-reactive-app branch 2 times, most recently from 0fcf2c2 to 9cb236c Compare December 1, 2024 01:17
The UserDetailsServiceAutoConfiguration is only to be active in a servlet based web application

See spring-projectsgh-43326
@mhalbritter mhalbritter changed the title Making UserDetailsServiceAutoConfiguration conditional Servlet-based UserDetailsServiceAutoConfiguration is active in a reactive app Dec 2, 2024
@mhalbritter mhalbritter added type: regression A regression from a previous release and removed status: waiting-for-triage An issue we've not yet triaged labels Dec 2, 2024
@mhalbritter mhalbritter added this to the 3.4.x milestone Dec 2, 2024
@mhalbritter mhalbritter self-assigned this Dec 2, 2024
@sephiroth-j
Copy link

It would be consequent to make ReactiveUserDetailsServiceAutoConfiguration conditional as well.

@mhalbritter
Copy link
Contributor

It would be consequent to make ReactiveUserDetailsServiceAutoConfiguration conditional as well.

I've opened #43345.

@mhalbritter
Copy link
Contributor

Thanks @BenchmarkingBuffalo !

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
type: regression A regression from a previous release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants