Skip to content
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

Do not auto-configure a UserDetailsService when an AuthenticationManagerResolver bean is present #28361

Closed

Conversation

bartoszJaszczak
Copy link
Contributor

Resolves #26766. As mentioned in the issue, AuthenticationManagerResolver was added to the ConditionalOnMissingBean in the UserDetailsServiceAutoConfiguration.

@pivotal-cla
Copy link

@bartoszJaszczak Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 15, 2021
@pivotal-cla
Copy link

@bartoszJaszczak Thank you for signing the Contributor License Agreement!

@mbhave mbhave added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged labels Oct 18, 2021
@mbhave mbhave added this to the 2.6.x milestone Oct 18, 2021
@wilkinsona wilkinsona self-assigned this Oct 19, 2021
@wilkinsona wilkinsona modified the milestones: 2.6.x, 2.6.0-RC1 Oct 19, 2021
@wilkinsona
Copy link
Member

@bartoszJaszczak Thanks very much for making your first contribution to Spring Boot.

@wilkinsona wilkinsona changed the title Extend ConditionalOnMissingBean in the UserDetailsServiceAutoConfiguration Do not auto-configure a UserDetailsService when an AuthenticationManagerResolver bean is present Oct 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default password should not be logged when AuthenticationManagerResolver bean is present
5 participants