| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313 | = OAuth 2.0 Bearer Tokens[[oauth2resourceserver-bearertoken-resolver]]== Bearer Token ResolutionBy default, Resource Server looks for a bearer token in the `Authorization` header.This, however, can be customized in a handful of ways.=== Reading the Bearer Token from a Custom HeaderFor example, you may have a need to read the bearer token from a custom header.To achieve this, you can expose a `DefaultBearerTokenResolver` as a bean, or wire an instance into the DSL, as you can see in the following example:.Custom Bearer Token Header[tabs]======Java::+[source,java,role="primary"]----@BeanBearerTokenResolver bearerTokenResolver() {    DefaultBearerTokenResolver bearerTokenResolver = new DefaultBearerTokenResolver();    bearerTokenResolver.setBearerTokenHeaderName(HttpHeaders.PROXY_AUTHORIZATION);    return bearerTokenResolver;}----Kotlin::+[source,kotlin,role="secondary"]----@Beanfun bearerTokenResolver(): BearerTokenResolver {    val bearerTokenResolver = DefaultBearerTokenResolver()    bearerTokenResolver.setBearerTokenHeaderName(HttpHeaders.PROXY_AUTHORIZATION)    return bearerTokenResolver}----Xml::+[source,xml,role="secondary"]----<http>    <oauth2-resource-server bearer-token-resolver-ref="bearerTokenResolver"/></http><bean id="bearerTokenResolver"        class="org.springframework.security.oauth2.server.resource.web.DefaultBearerTokenResolver">    <property name="bearerTokenHeaderName" value="Proxy-Authorization"/></bean>----======Or, in circumstances where a provider is using both a custom header and value, you can use `HeaderBearerTokenResolver` instead.=== Reading the Bearer Token from a Form ParameterOr, you may wish to read the token from a form parameter, which you can do by configuring the `DefaultBearerTokenResolver`, as you can see below:.Form Parameter Bearer Token[tabs]======Java::+[source,java,role="primary"]----DefaultBearerTokenResolver resolver = new DefaultBearerTokenResolver();resolver.setAllowFormEncodedBodyParameter(true);http    .oauth2ResourceServer(oauth2 -> oauth2        .bearerTokenResolver(resolver)    );----Kotlin::+[source,kotlin,role="secondary"]----val resolver = DefaultBearerTokenResolver()resolver.setAllowFormEncodedBodyParameter(true)http {    oauth2ResourceServer {        bearerTokenResolver = resolver    }}----Xml::+[source,xml,role="secondary"]----<http>    <oauth2-resource-server bearer-token-resolver-ref="bearerTokenResolver"/></http><bean id="bearerTokenResolver"        class="org.springframework.security.oauth2.server.resource.web.HeaderBearerTokenResolver">    <property name="allowFormEncodedBodyParameter" value="true"/></bean>----======== Bearer Token PropagationNow that your resource server has validated the token, it might be handy to pass it to downstream services.This is quite simple with `{security-api-url}org/springframework/security/oauth2/server/resource/web/reactive/function/client/ServletBearerExchangeFilterFunction.html[ServletBearerExchangeFilterFunction]`, which you can see in the following example:[tabs]======Java::+[source,java,role="primary"]----@Beanpublic WebClient rest() {    return WebClient.builder()            .filter(new ServletBearerExchangeFilterFunction())            .build();}----Kotlin::+[source,kotlin,role="secondary"]----@Beanfun rest(): WebClient {    return WebClient.builder()            .filter(ServletBearerExchangeFilterFunction())            .build()}----======When the above `WebClient` is used to perform requests, Spring Security will look up the current `Authentication` and extract any `{security-api-url}org/springframework/security/oauth2/core/AbstractOAuth2Token.html[AbstractOAuth2Token]` credential.Then, it will propagate that token in the `Authorization` header.For example:[tabs]======Java::+[source,java,role="primary"]----this.rest.get()        .uri("https://other-service.example.com/endpoint")        .retrieve()        .bodyToMono(String.class)        .block()----Kotlin::+[source,kotlin,role="secondary"]----this.rest.get()        .uri("https://other-service.example.com/endpoint")        .retrieve()        .bodyToMono<String>()        .block()----======Will invoke the `https://other-service.example.com/endpoint`, adding the bearer token `Authorization` header for you.In places where you need to override this behavior, it's a simple matter of supplying the header yourself, like so:[tabs]======Java::+[source,java,role="primary"]----this.rest.get()        .uri("https://other-service.example.com/endpoint")        .headers(headers -> headers.setBearerAuth(overridingToken))        .retrieve()        .bodyToMono(String.class)        .block()----Kotlin::+[source,kotlin,role="secondary"]----this.rest.get()        .uri("https://other-service.example.com/endpoint")        .headers{  headers -> headers.setBearerAuth(overridingToken)}        .retrieve()        .bodyToMono<String>()        .block()----======In this case, the filter will fall back and simply forward the request onto the rest of the web filter chain.[NOTE]Unlike the {security-api-url}org/springframework/security/oauth2/client/web/reactive/function/client/ServletOAuth2AuthorizedClientExchangeFilterFunction.html[OAuth 2.0 Client filter function], this filter function makes no attempt to renew the token, should it be expired.To obtain this level of support, please use the OAuth 2.0 Client filter.=== `RestTemplate` supportThere is no `RestTemplate` equivalent for `ServletBearerExchangeFilterFunction` at the moment, but you can propagate the request's bearer token quite simply with your own interceptor:[tabs]======Java::+[source,java,role="primary"]----@BeanRestTemplate rest() {	RestTemplate rest = new RestTemplate();	rest.getInterceptors().add((request, body, execution) -> {		Authentication authentication = SecurityContextHolder.getContext().getAuthentication();		if (authentication == null) {			return execution.execute(request, body);		}		if (!(authentication.getCredentials() instanceof AbstractOAuth2Token)) {			return execution.execute(request, body);		}		AbstractOAuth2Token token = (AbstractOAuth2Token) authentication.getCredentials();	    request.getHeaders().setBearerAuth(token.getTokenValue());	    return execution.execute(request, body);	});	return rest;}----Kotlin::+[source,kotlin,role="secondary"]----@Beanfun rest(): RestTemplate {    val rest = RestTemplate()    rest.interceptors.add(ClientHttpRequestInterceptor { request, body, execution ->        val authentication: Authentication? = SecurityContextHolder.getContext().authentication        if (authentication != null) {            execution.execute(request, body)        }        if (authentication!!.credentials !is AbstractOAuth2Token) {            execution.execute(request, body)        }        val token: AbstractOAuth2Token = authentication.credentials as AbstractOAuth2Token        request.headers.setBearerAuth(token.tokenValue)        execution.execute(request, body)    })    return rest}----======[NOTE]Unlike the {security-api-url}org/springframework/security/oauth2/client/OAuth2AuthorizedClientManager.html[OAuth 2.0 Authorized Client Manager], this filter interceptor makes no attempt to renew the token, should it be expired.To obtain this level of support, please create an interceptor using the xref:servlet/oauth2/client/index.adoc#oauth2client[OAuth 2.0 Authorized Client Manager].[[oauth2resourceserver-bearertoken-failure]]== Bearer Token FailureA bearer token may be invalid for a number of reasons. For example, the token may no longer be active.In these circumstances, Resource Server throws an `InvalidBearerTokenException`.Like other exceptions, this results in an OAuth 2.0 Bearer Token error response:[source,http request]----HTTP/1.1 401 UnauthorizedWWW-Authenticate: Bearer error_code="invalid_token", error_description="Unsupported algorithm of none", error_uri="https://tools.ietf.org/html/rfc6750#section-3.1"----Additionally, it is published as an `AuthenticationFailureBadCredentialsEvent`, which you can xref:servlet/authentication/events.adoc#servlet-events[listen for in your application] like so:[tabs]======Java::+[source,java,role="primary"]----@Componentpublic class FailureEvents {	@EventListener    public void onFailure(AuthenticationFailureBadCredentialsEvent badCredentials) {		if (badCredentials.getAuthentication() instanceof BearerTokenAuthenticationToken) {		    // ... handle        }    }}----Kotlin::+[source,kotlin,role="secondary"]----@Componentclass FailureEvents {    @EventListener    fun onFailure(badCredentials: AuthenticationFailureBadCredentialsEvent) {        if (badCredentials.authentication is BearerTokenAuthenticationToken) {            // ... handle        }    }}----======
 |