When developing and maintaining Vaadin Connect I want to rely on up-to-date and maintained 3rd party dependencies, thus I want it remove the dependency on Spring Security OAuth or to replace it with a dependency on its successor–Spring Security 5.
The Spring Security OAuth project is in maintenance mode. The up-to-date and maintained OAuth2 implementation is being incorporated into Spring Security 5. That includes Client, Resource Server and Authorization Server implementations.
OAuth 2.0 Resource Server was added in Spring Security 5.1.0 (link)
~OAuth 2.0 Authorization Server is planned for Spring Security 5.3.0 (link)~.
OAuth 2.0 Authorization Server is planned to be dropped from Spring Security, so we will need to look for another implementation if we are going to replace the one from Spring Security OAuth.
When developing and maintaining Vaadin Connect I want to rely on up-to-date and maintained 3rd party dependencies, thus I want it remove the dependency on Spring Security OAuth or to replace it with a dependency on its successor–Spring Security 5.
The Spring Security OAuth project is in maintenance mode. The up-to-date and maintained OAuth2 implementation is being incorporated into Spring Security 5. That includes Client, Resource Server and Authorization Server implementations.
OAuth 2.0 Resource Server was added in Spring Security 5.1.0 (link) ~OAuth 2.0 Authorization Server is planned for Spring Security 5.3.0 (link)~. OAuth 2.0 Authorization Server is planned to be dropped from Spring Security, so we will need to look for another implementation if we are going to replace the one from Spring Security OAuth.