disabling default security password when defining our own WebSecurityConfigurerAdapter
See original GitHub issueHi,
I upgraded my spring boot from 1.1.4.RELEASE to 1.1.8.RELEASE without any change in my code source. everything works fine, but I get Using default security password: xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
in my log, somehow in AuthenticationManagerConfiguration.BootDefaultingAuthenticationConfigurerAdapter.configure(AuthenticationManagerBuilder auth)
the condition auth.isConfigured()
return false.
Have you a suggestion to disable the default password??
Issue Analytics
- State:
- Created 9 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Remove "Using default security password" on Spring Boot
The default security password is configured inside Spring Boot's AuthenticationManagerConfiguration class. This class has a conditional annotation to prevent ...
Read more >29. Security - Spring
You can change the username and password by providing a spring.security.user.name and spring.security.user.password . The basic features you get by default in a ......
Read more >Spring Boot Security Auto-Configuration - Baeldung
A quick and practical guide to Spring Boot's default Spring Security configuration. ... For example, we can override the default password by adding...
Read more >Disabling the logging of Spring Security's Default Security ...
This security password can be used with the default user, user , and would allow anyone with access to your logs to be...
Read more >Conditionally Disabling or Overriding Spring Boot Security ...
To disable Security Auto-Configuration and add our own configuration, we need to exclude the SecurityAutoConfiguration class from ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m having a similar problem moving from 1.2.1 to 1.2.2. (my case is much simpler)
Has something changed in regards to the builders for the security configuration?
Thank you for the response. Per the previous comment I’m closing this as a duplicate of #2567