Simplify the way OIDC tenant id interceptors can be created #34706
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.
Fixes #34692.
This PR simplifies the way custom tenant resolver interceptors can be created, now one just has to extend
quarkus.oidc.TenantResolverInterceptor
and pass it the tenant id.Update the test to confirm the
hr
tenant configuration is picked up - this configuration adds a custom audience value - which causes401
when the test uses a token with another (default) audience but adding an audience expected by thehr
tenant fixes it.This option complements 2 other options, where either
TenantResolver
orTenantConfigResolver
can be used