Description
There are OAuth 2.0 Providers that are not spec-compliant making it difficult for user's to integrate with using oauth2Login()
.
For example, LinkedIn does not return the token_type
parameter in the Token Response even though it is required as per spec. However, Spring Security 5.1 allows you to customize the Token Response to workaround this issue.
This is just one example, but there are other OAuth 2.0 provider's that are either non-compliant or require custom/additional parameters and/or headers to make oauth2Login()
work.
We should consider adding out-of-the-box adaptors (connectors) for common OAuth 2.0 providers that are non-compliant. These adaptors would come with pre-configured properties (similar to CommonOAuth2Provider
) as well with configured components required by oauth2Login()
, for example, OAuth2AccessTokenResponseClient
, OAuth2UserService
, etc.