Fix a disabled OidcClient REST client issue #40894
Merged
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.
The earlier update which I thought was obviously fixing it was correct but incomplete (or may be I tried something with Resteasy Classic which made me believe it was complete, unfortunately I don't remember now).
So this PR fixes it properly and this fix is supported by the test.
The test adds a disabled OidcClient tenant, the flow is: test calls FrontentResource which uses RESTClient to call a secured ProtectedResource - which can only be accessed if OidcClient acquired the token. But because OidcClient is disabled, the request to ProtectedResource goes without the token (as opposed to be terminated with DisabledOidcClientException) and therefore 401 is returned from ProtectedResource and is passed further back to the test code to confirm
DisabledOidcClientException
#40886