GitHub-Spring
/
spring-security
mirror of https://github.com/spring-projects/spring-security.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Fix typo 

Signed-off-by: Tran Ngoc Nhan <ngocnhan.tran1996@gmail.com>
pull/16838/head
Tran Ngoc Nhan 9 months ago committed by Josh Cummings
parent
bdbf6a2be3
commit
3be8e92187
2 changed files with 2 additions and 2 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      docs/modules/ROOT/pages/migration/oauth2.adoc
  2. 2
      docs/modules/ROOT/pages/reactive/oauth2/resource-server/opaque-token.adoc

2
docs/modules/ROOT/pages/migration/oauth2.adoc
Unescape View File

@ -2,7 +2,7 @@
== Validate `typ` Header with `JwtTypeValidator` == Validate `typ` Header with `JwtTypeValidator`
`NimbusJwtDecoder` in Spring Security 7 will move `typ` header validation to `JwtTypeValidator` intsead of relying on Nimbus. `NimbusJwtDecoder` in Spring Security 7 will move `typ` header validation to `JwtTypeValidator` instead of relying on Nimbus.
This brings it in line with `NimbusJwtDecoder` validating claims instead of relying on Nimbus to validate them. This brings it in line with `NimbusJwtDecoder` validating claims instead of relying on Nimbus to validate them.
If you are changing Nimbus's default type validation in a `jwtProcessorCustomizer` method, then you should move that to `JwtTypeValidator` or an implementation of `OAuth2TokenValidator` of your own. If you are changing Nimbus's default type validation in a `jwtProcessorCustomizer` method, then you should move that to `JwtTypeValidator` or an implementation of `OAuth2TokenValidator` of your own.

2
docs/modules/ROOT/pages/reactive/oauth2/resource-server/opaque-token.adoc
Unescape View File

@ -398,7 +398,7 @@ fun springSecurityFilterChain(http: ServerHttpSecurity): SecurityWebFilterChain
---- ----
====== ======
This is handy when deeper configuration, such as <<webflux-oauth2resourceserver-opaque-authorization-extraction,authority mapping>>or <<webflux-oauth2resourceserver-opaque-jwt-introspector,JWT revocation>>, is necessary. This is handy when deeper configuration, such as <<webflux-oauth2resourceserver-opaque-authorization-extraction,authority mapping>> or <<webflux-oauth2resourceserver-opaque-jwt-introspector,JWT revocation>>, is necessary.
[[webflux-oauth2resourceserver-opaque-introspector-bean]] [[webflux-oauth2resourceserver-opaque-introspector-bean]]
=== Exposing a `ReactiveOpaqueTokenIntrospector` `@Bean` === Exposing a `ReactiveOpaqueTokenIntrospector` `@Bean`

Write Preview
Loading…
Cancel
Save