Ryan Baxter
Ryan Baxter
Is `data-auth-server` actually a host name that DNS would resolve? It seems like an issue with your environment rather than an issue with Spring Cloud Security.
Sure we would be happy to review an enhancement
@ArtyomGabeev are you not sure where the documentation is, or where to put it in the documentation itself
Can you provide a [complete, minimal, verifiable sample](https://stackoverflow.com/help/mcve) that reproduces the problem? It should be available as a GitHub (or similar) project or attached to this issue as a zip...
The NPE looks like a problem in Spring Security, it does not look a problem with Spring Cloud Security (from what I can see in the stack trace). I suggest...
We did another release because we had a lot of requests for some fixes there. So despite official support has ended for it, we did it for the benefit of...
Config clients may use WebFlux. Bus does not use Project Reactor at all and is using Spring Cloud Stream, I dont see why it would need to use Project Reactor.
Support sending events to clients with HTTP instead of AMPQ / kafka with Spring Cloud Config Monitor
This would require the config server to know all the endpoints of the clients (or use something like the discovery server to discover them).
It's just printing a warning message most likely. Does the config server still work, can it serve the configuration?
Here is the original PR https://github.com/spring-cloud/spring-cloud-config/pull/1628/files Is there anything in the logs indicating what might be wrong?