Expected Behavior
It should works the same as the old implementation but hopefully reactive. You will also need to replace @EnableAuthorizationServer with @EnableReactiveAuthorizationServer
Context
Goal: Support projects with older version of spring looking to convert to reactive and/or waiting for Spring Authorization Server project to be released with reactive implementation.
Please checkout this repository: spring-reactive-authorization-server
Comment From: eleftherias
Thanks for reaching out @VuDo98. The authorization server support was part of the legacy Spring Security OAuth project, which is deprecated. That means we are not adding any more features to that project. We are working on experimental Authorization Server support in the Spring Authorization Server project, although WebFlux support is not on the roadmap as of now.
Comment From: voduku
@eleftherias Hi, thanks for answering. I am actually not asking for reactive support but I am asking if my implementation of the deprecated authorization would be an acceptable temporary reactive support and would you guys be able to have a quick look at my work to review it. I already did the work and I pretty much keep the old logic but just coded it reactively. I believe there are many projects still use the deprecated version and it will take a long time for the new authorization server to be released and support webflux.
Comment From: eleftherias
Hi @VuDo98 Given that the legacy Spring Security OAuth project is deprecated and we aren't adding new features, it doesn't make sense to add reactive support. This applies whether it is in the spring-security-oauth repository or a different repository.