netflix-commons | Common utilities for Netflix OSS projects | GraphQL library

This might have to do with you not using Generics with your java Collections

Well the correct term is that @EnableAuthorizationServer is in maintenance mode which basically means deprecated. As in there will be no added features or updates.

The story goes basically as follows.

During Spring 4 i believe there was a single person that maintained the oauth2 part of spring security. When Spring security 5 was launched the team at pivotal decided to do a major overhaul of spring security and the oauth2 parts. So what they did was to drop Authorisation server support, and instead focus on the Resource server support at first.

Spring announcement of dropping Authorisation server support

You have pulled in spring-cloud-starter-oauth2 which in turn har a peer dependency on spring-security-oauth2-autoconfigure which in turn pulls in spring-security-oauth2.

Here Spring clearly states that if you wish to use spring-security-oauth2 they will help you out, but it is in maintenance mode.

The choice to not support it was made because an authorization server is like owning a product. Spring doesn't maintain their own database, or own Ldap server etc. There are plenty of auth servers out there that can be used, okta, curity, github, fb, google, etc, etc.

But Spring has actually reevaluated that choice and decided to start a community developed open source authorisation server

So you have 3 choices:

• use the old, that is in maintenance mode
• use a 3rd party vendor, github, fb, google, okta, curity etc.
• try out the new open source authorisation server

There might be easier methods but this is what I can do now ... probably can be narrowed down to a single line with some tweaking

In this particular case, one of the library(jar) from application's WEB-INF/lib directory was causing this issue and the jar is...