Skip to content

Update docs to use multi-tenancy #10829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update docs to use multi-tenancy #10829

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/modules/ROOT/pages/reactive/oauth2/resource-server/multitenancy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
= OAuth 2.0 Resource Server Multitenancy
= OAuth 2.0 Resource Server Multi-tenancy

[[webflux-oauth2resourceserver-multitenancy]]
== Multi-tenancy
Expand Down
4 changes: 2 additions & 2 deletions docs/modules/ROOT/pages/servlet/oauth2/resource-server/multitenancy.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
= OAuth 2.0 Resource Server Multitenancy
= OAuth 2.0 Resource Server Multi-tenancy

[[oauth2reourceserver-opaqueandjwt]]
== Supporting both JWT and Opaque Token
Expand Down Expand Up @@ -100,7 +100,7 @@ In each case, there are two things that need to be done and trade-offs associate

One way to differentiate tenants is by the issuer claim. Since the issuer claim accompanies signed JWTs, this can be done with the `JwtIssuerAuthenticationManagerResolver`, like so:

.Multitenancy Tenant by JWT Claim
.Multi-tenancy Tenant by JWT Claim
====
.Java
[source,java,role="primary"]
Expand Down