- Use withJwkSetUri instead of fromJwkSetUri
- Use ES512 instead of EC512
- Use NimbusReactiveOpaqueTokenIntrospector instead of NimbusOpaqueTokenIntrospector in reactive
- User authorizeExchange instead of authorizeRequests
@ -271,7 +271,7 @@ For greater power, though, we can use a builder that ships with `NimbusReactiveJ
@@ -271,7 +271,7 @@ For greater power, though, we can use a builder that ships with `NimbusReactiveJ
@ -282,8 +282,8 @@ Calling `jwsAlgorithm` more than once will configure `NimbusReactiveJwtDecoder`
@@ -282,8 +282,8 @@ Calling `jwsAlgorithm` more than once will configure `NimbusReactiveJwtDecoder`
@ -789,7 +789,7 @@ Or, exposing a `ReactiveOpaqueTokenIntrospector` `@Bean` has the same effect as
@@ -789,7 +789,7 @@ Or, exposing a `ReactiveOpaqueTokenIntrospector` `@Bean` has the same effect as
----
@Bean
public ReactiveOpaqueTokenIntrospector introspector() {
return new NimbusOpaqueTokenIntrospector(introspectionUri, clientId, clientSecret);
return new NimbusReactiveOpaqueTokenIntrospector(introspectionUri, clientId, clientSecret);
}
----
@ -1036,8 +1036,8 @@ JwtIssuerReactiveAuthenticationManagerResolver authenticationManagerResolver = n
@@ -1036,8 +1036,8 @@ JwtIssuerReactiveAuthenticationManagerResolver authenticationManagerResolver = n
@ -496,7 +496,7 @@ For greater power, though, we can use a builder that ships with `NimbusJwtDecode
@@ -496,7 +496,7 @@ For greater power, though, we can use a builder that ships with `NimbusJwtDecode
@ -507,8 +507,8 @@ Calling `jwsAlgorithm` more than once will configure `NimbusJwtDecoder` to trust
@@ -507,8 +507,8 @@ Calling `jwsAlgorithm` more than once will configure `NimbusJwtDecoder` to trust