Disabling the logging of Spring Security's Default Security Password

If you use Spring Boot and Spring Security, you may recognise the following from your logs:

2020-06-19 08:54:32.698  INFO 14983 --- [           main] .s.s.UserDetailsServiceAutoConfiguration :

Using generated security password: 2ec7edf2-4fe0-4f25-878e-9f4f50001d06

This security password can be used with the default user, user, and would allow anyone with access to your logs to be able to authenticate to your service. This is a bad thing!

So how do we stop that? We've got a few options below, in order of my preference. Each of these have been tested with Spring Boot and Spring Security v2.3.1.RELEASE.

Excluding the autoconfiguration class

To prevent this user from being auto-configured, we can exclude the autoconfiguration class, which means Spring Security won't set up, and log, the default user.

We can do this on our main application class:

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.autoconfigure.security.servlet.UserDetailsServiceAutoConfiguration;

@SpringBootApplication(exclude = {UserDetailsServiceAutoConfiguration.class})
public class Application {
  public static void main(String[] args) {
    SpringApplication.run(Application.class, args);

Or via a properties file:


Overriding the AuthenticationManager

Alternatively, we can follow Stefan's comment on Remove “Using default security password” on Spring Boot:

import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.security.authentication.AuthenticationManager;
import org.springframework.security.config.annotation.authentication.builders.AuthenticationManagerBuilder;
import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;
import org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter;

public class MyCustomSecurityConfig extends WebSecurityConfigurerAdapter { // via https://stackoverflow.com/a/41856630/2257038

  protected void configure(AuthenticationManagerBuilder authManager) throws Exception {
    // This is the code you usually have to configure your authentication manager.
    // This configuration will be used by authenticationManagerBean() below.

  public AuthenticationManager authenticationManagerBean() throws Exception {
    return super.authenticationManagerBean();

By providing a custom bean that overrides the AuthenticationManagerBuilder, we can replace the autogenerated beans with our own, which would mean that UserDetailsServiceAutoConfiguration doesn't get triggered.

Disabling logging for that class

Alternatively, if we want it to be autoconfigured, but not logged, we can change the logging configuration for that class:

# completely remove it
# or only log WARN and above

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#blogumentation #spring-boot #spring-security.

This post was filed under articles.

Has this content helped you? Please consider supporting me so I can continue to create content like this!

Related Posts

Other posts you may be interested in:

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.