Phil Clay e5fca61810 Introduce Reactive OAuth2Authorization success/failure handlers ... All ReactiveOAuth2AuthorizedClientManagers now have authorization success/failure handlers. A success handler is provided to save authorized clients for future requests. A failure handler is provided to remove previously saved authorized clients. ServerOAuth2AuthorizedClientExchangeFilterFunction also makes use of a failure handler in the case of unauthorized or forbidden http status code. The main use cases now handled are - remove authorized client when an authorization server indicates that a refresh token is no longer valid (when authorization server returns invalid_grant) - remove authorized client when a resource server indicates that an access token is no longer valid (when resource server returns invalid_token) Introduced ClientAuthorizationException to capture details needed when removing an authorized client. All ReactiveOAuth2AccessTokenResponseClients now throw a ClientAuthorizationException on failures. Created AbstractWebClientReactiveOAuth2AccessTokenResponseClient to unify common logic between all ReactiveOAuth2AccessTokenResponseClients. Fixes gh-7699		2020-01-16 15:24:55 -05:00
..
main/java/org/springframework/security/oauth2/client	Introduce Reactive OAuth2Authorization success/failure handlers	2020-01-16 15:24:55 -05:00
test	Introduce Reactive OAuth2Authorization success/failure handlers	2020-01-16 15:24:55 -05:00