Refine subscription strategy for Servlet ExchangeFilterFunctions #7423
Labels
in: oauth2
An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)
type: enhancement
A general enhancement
Milestone
Related to #7422
There are two Servlet-based ExchangeFilterFunctions in the code base:
ServletBearerExchangeFilterFunction
ServletOAuth2AuthorizedClientExchangeFilterFunction
They both rely on the registration of a
CoreSubscriber
that populates the ReactorContext
with the currentAuthentication
.The subscriber instances and the actual registrations are different. This means that there are two keys in the Reactor Context, both of which contain the current
Authentication
when likely only one would suffice.The text was updated successfully, but these errors were encountered: