NimbusReactiveJwtDecoder.JwkSetUriReactiveJwtDecoderBuilder holds a reference to JWSVerificationKeySelector before ConfigurableJWTProcessor.setJWSKeySelector is executed #12960
Labels
in: oauth2
An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)
type: bug
A general bug
Milestone
The
ConfigurableJWTProcessor.setJWSKeySelector(JWSKeySelector)
is unable to update the reference used byNimbusReactiveJwtDecoder.JwkSetUriReactiveJwtDecoderBuilder.processor()
. The processor holds a reference to the defaultJWSKeySelector
created withinNimbusReactiveJwtDecoder.JwkSetUriReactiveJwtDecoderBuilder.jwsKeySelector()
via a method reference withinJwkSetUriReactiveJwtDecoderBuilder.getExpectedJwsAlgorithms()
before theConfigurableJWTProcessorsetJWSKeySelector(JWSKeySelector)
is executed.The following unit test will show that the processor is executing the wrong
JWSVerificationKeySelector.isAllowed(JWSAlgorithm)
reference.The text was updated successfully, but these errors were encountered: