Describe the bug

OIDC Multitenancy Client setup

When developing a multitenant-aware quarkus application with dynamic tenant resolution, developers need to implement a io.quarkus.oidc.TenantConfigResolver to pick the OIDC realm from the inbound call. It is rational/usable to supply the realmId as a segment within the service's resource path. Resolving the realmID in this way implies that the service can be fully multi-tenant with minimal adaptions to the codebase.

This is not documented on the quarkus OIDC site, so I will supply a small example to capture this pattern.

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

Will supply a PR on the documentation to cover this.