OAuth2AuthorizedClientManager implementation works outside of request

[jgrandja]

Fixes gh-6780

Related #6683

NOTE: This PR is rebased off #7352. Please review the most recent commit, which includes all the changes for this PR.

[rwinch]

If we want this to work outside of the scope of an HttpServletRequest we should not require HttpServletRequest on the classpath. I haven't looked at how we would do this yet, so some research would be necessary

[jgrandja]

@rwinch

If we want this to work outside of the scope of an HttpServletRequest we should not require HttpServletRequest on the classpath

The use case we're trying to realize is the ability for a client to obtain an access token outside of a HttpServletRequest context, for example, in a @Scheduled process but still running in a web (Servlet) app. In addition to this, user's could directly leverage DefaultOAuth2AuthorizedClientManager in the service or data tier without depending on HttpServletRequest and HttpServletResponse.

For more details, please see this comment and this one:

I think there should be a way to just grab new access tokens in the service/data tier of a web application (for one to many authenticated clients) while using RestTemplate if desired

[jzheaux]

Would you please explain your reasoning for this name? Traditionally, I'd read this as "A class that serves OAuth2AuthorizedClientManagers", kind of like how OAuth2AuthorizedClientService serves OAuth2AuthorizedClients.

Maybe ServiceOAuth2AuthorizedClientManager is better since it places the thing that it is (an OAuth2AuthorizedClientManager) at the end and the thing it's reliant on (the OAuth2AuthorizedClientService) at the beginning of the name?

[jzheaux]

Talked with @jgrandja and looks like we'll rename this to AuthorizedClientServiceOAuth2AuthorizedClientManager so that the interface it's implementing goes at the end.

[jzheaux]

@jgrandja I've approved the changes, pending the class rename.

[jgrandja]

Merged via f7d0385