Allow java.lang.Long in whitelist for Jackson security

[mvitz]

Expected Behavior

When using spring-security-oauth2-client in combination with spring-session-data-redis and enabling JSON serializing via

@Bean
public RedisSerializer<Object> springSessionDefaultRedisSerializer() {
    var om = new ObjectMapper();
    om.registerModules(SecurityJackson2Modules.getModules(loader));
    return new GenericJackson2JsonRedisSerializer(om);
}

the session should be successfully deserialized when containing a type of java.lang.Long.

Current Behavior

The deserialization fails with the exception:

org.springframework.data.redis.serializer.SerializationException: Could not read JSON: The class with java.lang.Long and name of java.lang.Long is not in the allowlist. If you believe this class is safe to deserialize, please provide an explicit mapping using Jackson annotations or by providing a Mixin. If the serialization is only done by a trusted source, you can also enable default typing. See https://github.com/spring-projects/spring-security/issues/4370 for details (through reference chain: org.springframework.security.core.context.SecurityContextImpl["authentication"]->org.springframework.security.oauth2.client.authentication.OAuth2AuthenticationToken["principal"]->org.springframework.security.oauth2.core.oidc.user.DefaultOidcUser["authorities"]->org.springframework.security.oauth2.core.oidc.user.OidcUserAuthority["idToken"]->org.springframework.security.oauth2.core.oidc.OidcIdToken["claims"])

Context

At least our Okta returns a claim ver with a java.lang.Long of 1. When persisting the spring-security session with spring-session as JSON within redis this is serialized as

...
                "ver": [
                  "java.lang.Long",
                  1
                ],
...

and can not be deserialized because java.lang.Long is not within the allow list.

As a workaround, I can fall back to storing the session not as JSON.

[TolstovM]

Hello!
As a workaround you can create LongMixin
public abstract class LongMixin { }
and add it to your objectMapper

mapper.addMixIn(Long.class, LongMixin.class);

It works fine for me.

[TolstovM]

I've added PR, which would fix this issue #12584

[marcusdacoregio]

I think that this is related to spring-projects/spring-session#2227

[TolstovM]

@marcusdacoregio Yep, it is

[marcusdacoregio]

Hi @mvitz, which version of Spring Security and Spring Session are you using?

[mvitz]

I think I was playing around with Spring Boot 3.0.0 which would resolve to:

• Spring Security: 6.0.0
• Spring Session: 3.0.0

[mvitz]

After upgrading to Boot 3.0.2 (including 6.0.1) the same exception keeps occuring.