Fixing the tenant annotation check order in the OIDC renant resolver #39949
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does a minor OIDC tenancy doc update, as the Table of content is misaligned right now starting from https://quarkus.io/version/main/guides/security-openid-connect-multitenancy#tenant-resolution-order, so hopefully, after this PR, it will be much clearer from TOC alone what the order is.
And it does a minor optimization/fix to the OIDC DefaultTenantConfigResolver to align it with the docs: if the
@Tenant
annotation was used to resolve the tenant id, calling the dynamic customTenantConfigResolver
is wrong, I missed it during the recent refactoring which is all still onmain
only