Browse Source
When OAuth2ResourceServerConfigurer.authenticationManagerResolver() is configured, it now takes precedence over any jwt() or opaqueToken() configuration without throwing an exception. This follows Spring Security's convention where specialized configurations take precedence over general ones at runtime. The solution removes the validation check that prevented authenticationManagerResolver from being used with jwt/opaqueToken configurations, allowing for more flexible configuration scenarios such as those needed by Spring Authorization Server when supporting both JWT and opaque tokens. Closes gh-16406 Signed-off-by: academey <academey@gmail.com>pull/17676/head
2 changed files with 49 additions and 11 deletions
Loading…
Reference in new issue