Describe the bug
The bug itself is really simple. Version 6.5 introduces JwtTypeValidator that is meant to replace Nimbus type validators. While making migrations to incoming Spring boot 4.0 I noticed that this validator is case sensitive and previously used Nimbus JOSEObjectTypeVerifier is not.
Expected behavior
new JwtTypeValidator should be backward compatible with JOSEObjectTypeVerifier
Those two classes are really similar but Spring native implementation uses Strings as type values when JOSEObjectTypeVerifier uses JOSEObjectType with overridden equals that is not case sensitive.
Describe the bug
The bug itself is really simple. Version 6.5 introduces JwtTypeValidator that is meant to replace Nimbus type validators. While making migrations to incoming Spring boot 4.0 I noticed that this validator is case sensitive and previously used Nimbus JOSEObjectTypeVerifier is not.
Expected behavior
new JwtTypeValidator should be backward compatible with JOSEObjectTypeVerifier
Those two classes are really similar but Spring native implementation uses Strings as type values when JOSEObjectTypeVerifier uses JOSEObjectType with overridden equals that is not case sensitive.