For the latest stable version, please use Spring Security 6.4.1!spring-doc.cn

Preparing for 6.0

The Spring Security team has prepared the 5.8 release to simplify upgrading to Spring Security 6.0. Use 5.8 and the steps below to minimize changes when updating to 6.0.spring-doc.cn

Update to Spring Security 5.8

The first step is to ensure you are the latest patch release of Spring Boot 2.7. Next, you should ensure you are on the latest patch release of Spring Security 5.8. If you are using Spring Boot, you will need to override the Spring Boot version from Spring Security 5.7 to 5.8. Spring Security 5.8 is fully compatible with Spring Security 5.7 and thus Spring Boot 2.7. For directions, on how to update to Spring Security 5.8 visit the Getting Spring Security section of the reference guide.spring-doc.cn

Update Password Encoding

In 6.0, password encoding minimums are updated for PBKDF2, SCrypt, and Argon2.spring-doc.cn

If you are using the default password encoder, then there are no preparation steps to follow and this section can be skipped.spring-doc.cn

Update Pbkdf2PasswordEncoder

If you are using Pbkdf2PasswordEncoder, the constructors are replaced with static factories that refer to the Spring Security version that the given settings apply to.spring-doc.cn

Replace Deprecated Constructor Usage

If you use the default constructor, you should begin by changing:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    return new Pbkdf2PasswordEncoder();
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    return Pbkdf2PasswordEncoder()
}

to:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    return Pbkdf2PasswordEncoder.defaultsForSpringSecurity_v5_5();
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    return Pbkdf2PasswordEncoder.defaultsForSpringSecurity_v5_5()
}

Or, if you have custom settings, change to the constructor that specifies all settings, like so:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    PasswordEncoder current = new Pbkdf2PasswordEncoder("mysecret".getBytes(UTF_8), 320000);
    return current;
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    val current: PasswordEncoder = Pbkdf2PasswordEncoder("mysecret".getBytes(UTF_8), 320000)
    return current
}

Change them to use the fully-specified constructor, like the following:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    PasswordEncoder current = new Pbkdf2PasswordEncoder("mysecret".getBytes(UTF_8), 16, 185000, 256);
    return current;
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    val current: PasswordEncoder = Pbkdf2PasswordEncoder("mysecret".getBytes(UTF_8), 16, 185000, 256)
    return current
}

Use DelegatingPasswordEncoder

Once you are not using the deprecated constructor, the next step is to prepare your code to upgrade to the latest standards by using DelegatingPasswordEncoder. The following code configures the delegating encoder to detect passwords that are using current and replace them with the latest:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    String prefix = "[email protected]";
    PasswordEncoder current = // ... see previous step
    PasswordEncoder upgraded = Pbkdf2PasswordEncoder.defaultsForSpringSecurity_v5_8();
    DelegatingPasswordEncoder delegating = new DelegatingPasswordEncoder(prefix, Map.of(prefix, upgraded));
    delegating.setDefaultPasswordEncoderForMatches(current);
    return delegating;
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    String prefix = "[email protected]"
    PasswordEncoder current = // ... see previous step
    PasswordEncoder upgraded = Pbkdf2PasswordEncoder.defaultsForSpringSecurity_v5_8()
    DelegatingPasswordEncoder delegating = new DelegatingPasswordEncoder(prefix, Map.of(prefix, upgraded))
    delegating.setDefaultPasswordEncoderForMatches(current)
    return delegating
}

Update SCryptPasswordEncoder

If you are using SCryptPasswordEncoder, the constructors are replaced with static factories that refer to the Spring Security version that the given settings apply to.spring-doc.cn

Replace Deprecated Constructor Usage

If you use the default constructor, you should begin by changing:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    return new SCryptPasswordEncoder();
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    return SCryptPasswordEncoder()
}

to:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    return SCryptPasswordEncoder.defaultsForSpringSecurity_v4_1();
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    return SCryptPasswordEncoder.defaultsForSpringSecurity_v4_1()
}

Use DelegatingPasswordEncoder

Once you are not using the deprecated constructor, the next step is to prepare your code to upgrade to the latest standards by using DelegatingPasswordEncoder. The following code configures the delegating encoder to detect passwords that are using current and replace them with the latest:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
    String prefix = "[email protected]";
    PasswordEncoder current = // ... see previous step
    PasswordEncoder upgraded = SCryptPasswordEncoder.defaultsForSpringSecurity_v5_8();
    DelegatingPasswordEncoder delegating = new DelegatingPasswordEncoder(prefix, Map.of(prefix, upgraded));
    delegating.setDefaultPasswordEncoderForMatches(current);
    return delegating;
}
@Bean
fun passwordEncoder(): PasswordEncoder {
    String prefix = "[email protected]"
    PasswordEncoder current = // ... see previous step
    PasswordEncoder upgraded = SCryptPasswordEncoder.defaultsForSpringSecurity_v5_8()
    DelegatingPasswordEncoder delegating = new DelegatingPasswordEncoder(prefix, Map.of(prefix, upgraded))
    delegating.setDefaultPasswordEncoderForMatches(current)
    return delegating
}

Update Argon2PasswordEncoder

If you are using Argon2PasswordEncoder, the constructors are replaced with static factories that refer to the Spring Security version that the given settings apply to.spring-doc.cn

Replace Deprecated Constructor Usage

If you use the default constructor, you should begin by changing:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
	return new Argon2PasswordEncoder();
}
@Bean
fun passwordEncoder(): PasswordEncoder {
	return Argon2PasswordEncoder()
}

to:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
	return Argon2PasswordEncoder.defaultsForSpringSecurity_v5_2();
}
@Bean
fun passwordEncoder(): PasswordEncoder {
	return Argon2PasswordEncoder.defaultsForSpringSecurity_v5_2()
}

Use DelegatingPasswordEncoder

Once you are not using the deprecated constructor, the next step is to prepare your code to upgrade to the latest standards by using DelegatingPasswordEncoder. The following code configures the delegating encoder to detect passwords that are using current and replace them with the latest:spring-doc.cn

@Bean
PasswordEncoder passwordEncoder() {
	String prefix = "[email protected]";
	PasswordEncoder current = // ... see previous step
    PasswordEncoder upgraded = Argon2PasswordEncoder.defaultsForSpringSecurity_v5_8();
	DelegatingPasswordEncoder delegating = new DelegatingPasswordEncoder(prefix, Map.of(prefix, upgraded));
	delegating.setDefaultPasswordEncoderForMatches(current);
	return delegating;
}
@Bean
fun passwordEncoder(): PasswordEncoder {
	String prefix = "[email protected]"
	PasswordEncoder current = // ... see previous step
    PasswordEncoder upgraded = Argon2PasswordEncoder.defaultsForSpringSecurity_v5_8()
	DelegatingPasswordEncoder delegating = new DelegatingPasswordEncoder(prefix, Map.of(prefix, upgraded))
	delegating.setDefaultPasswordEncoderForMatches(current)
	return delegating
}

Stop using Encryptors.queryableText

Encryptors.queryableText(CharSequence,CharSequence) is unsafe since the same input data will produce the same output. It was deprecated and will be removed in 6.0; Spring Security no longer supports encrypting data in this way.spring-doc.cn

To upgrade, you will either need to re-encrypt with a supported mechanism or store it decrypted.spring-doc.cn

Consider the following pseudocode for reading each encrypted entry from a table, decrypting it, and then re-encrypting it using a supported mechanism:spring-doc.cn

TextEncryptor deprecated = Encryptors.queryableText(password, salt);
BytesEncryptor aes = new AesBytesEncryptor(password, salt, KeyGenerators.secureRandom(12), CipherAlgorithm.GCM);
TextEncryptor supported = new HexEncodingTextEncryptor(aes);
for (MyEntry entry : entries) {
	String value = deprecated.decrypt(entry.getEncryptedValue()); (1)
	entry.setEncryptedValue(supported.encrypt(value)); (2)
	entryService.save(entry)
}
1 - The above uses the deprecated queryableText to convert the value to plaintext.
2 - Then, the value is re-encrypted with a supported Spring Security mechanism.

Please see the reference manual for more information on what encryption mechanisms Spring Security supports.spring-doc.cn

Perform Application-Specific Steps

Next, there are steps you need to perform based on whether it is a Servlet or Reactive application.spring-doc.cn