Skip to content

Refine subscription strategy for Servlet ExchangeFilterFunctions #7423

Closed
@jzheaux

Description

@jzheaux

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 Reactor Context with the current Authentication.

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.

Metadata

Metadata

Assignees

Labels

in: oauth2An issue in OAuth2 modules (oauth2-core, oauth2-client, oauth2-resource-server, oauth2-jose)type: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions