From 8872d8b7d084cc6fa3cfdb619b2f5ad44d5ffd27 Mon Sep 17 00:00:00 2001
From: Josh Cummings <josh.cummings@gmail.com>
Date: Tue, 24 Mar 2020 15:24:43 -0600
Subject: [PATCH] Polish Resource Server Multi-tenancy Docs

Issue gh-7532
---
 .../_includes/servlet/oauth2/oauth2-resourceserver.adoc      | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/manual/src/docs/asciidoc/_includes/servlet/oauth2/oauth2-resourceserver.adoc b/docs/manual/src/docs/asciidoc/_includes/servlet/oauth2/oauth2-resourceserver.adoc
index 3db8fbdbf19..25c8cf0d5eb 100644
--- a/docs/manual/src/docs/asciidoc/_includes/servlet/oauth2/oauth2-resourceserver.adoc
+++ b/docs/manual/src/docs/asciidoc/_includes/servlet/oauth2/oauth2-resourceserver.adoc
@@ -1604,8 +1604,7 @@ AuthenticationManagerResolver<HttpServletRequest> tokenAuthenticationManagerReso
     OpaqueTokenAuthenticationProvider opaqueToken = opaqueToken();
 
     return request -> {
-        String token = bearerToken.resolve(request);
-        if (isAJwt(token)) {
+        if (useJwt(request)) {
             return jwt::authenticate;
         } else {
             return opaqueToken::authenticate;
@@ -1614,6 +1613,8 @@ AuthenticationManagerResolver<HttpServletRequest> tokenAuthenticationManagerReso
 }
 ----
 
+NOTE: The implementation of `useJwt(HttpServletRequest)` will likely depend on custom request material like the path.
+
 And then specify this `AuthenticationManagerResolver` in the DSL:
 
 .Authentication Manager Resolver