Move OIDC propagation annotation to oidc-client #29147
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.
This PR is a follow up to #29130 and is about making it possible to register the
oidc-token-propagation-reactive
filter the same way it is current possible for theoidc-token-propagation
filter, using a common@AccessToken
annotation without having to use@RegisterProvider
and a complete filter class name, similar to what has been done withoidc-client-reactive-filter
with these commits: #28451 and #28472@AccessToken
is moved fromoidc-token-propagation
down tooidc-client
oidc-token-propagation-reactive
has been updated to support@AccessToken
oidc-token-propagation-reactive
test has been updated to show the differenceCC @rsvoboda @geoand