0

We have a gateway generated through jhipster that we cannot get working on production (rancher or aws). Our company has a server proxy that we need to get through to connect to Okta. It does not appear that webflux will allow us to supply our server proxy, so we get "connection refused" errors.

Has anyone run into this? Is there a workaround?

Edit: Working fine on local.

C Learly
  • 1
  • 1
  • 1
    Spring's proxy server documentation might help: https://docs.spring.io/spring-boot/docs/current/reference/html/howto.html#howto.webserver.use-behind-a-proxy-server – Matt Raible Aug 17 '21 at 21:59
  • Hi Matt, that didn't work for our case. I saw here https://github.com/okta/okta-spring-boot#proxy that WebFlux does not support proxy configuration. We're not behind a reverse proxy, but a regular proxy. I was hoping there was some sort of workaround, since jhipster gateway is webflux by default. – C Learly Aug 18 '21 at 17:06
  • Here's a couple of resources my colleagues mentioned might help. https://github.com/spring-projects/spring-security/issues/8882 and https://stackoverflow.com/a/66640554 – Matt Raible Aug 19 '21 at 11:50
  • We investigated those options and whatever they're doing does not seem to work. It's a Spring issue. It initiates a new resttemplate, so any overrides we attempt are erased. I appreciate your efforts to help. At this point, we'll just have to downgrade the app. – C Learly Aug 20 '21 at 18:30

0 Answers0