Spring Security Integration with Project Reactor

I have an application that relies on authentication associated with the request flow (for example, when invoking external REST services, the identity is transparently passed in the outgoing HTTP header using a request interceptor on the RestTemplate).

I am involved in learning and applying reactive templates in this application using Project Reactor and started by making my REST avi calls responsive. They use the pool Schedulers.elastic()

and result in the loss of Spring Security Context. Even if I switched to using the InheritableThreadLocal context holder strategy, the elastic pool will mix things up.

I'm looking for advice from people who have more experience with this topic about the best and most transparent pattern I could apply in this case. I have not yet managed to find any really attractive solution for this problem.

Is there any extension to Reactor or Spring Security that removes this inconvenience? Is there any extension point in Project Reactor that I could use?

+3


source to share


1 answer


Reactive support is a big topic for Spring Security 5. Phase One



0


source







All Articles