Azure APIM with self-hosted gateway

Question

Azure APIM with self-hosted gateway

Bollaert, Igor 17

We are currently test driving Azure APIM and attempting to set up a self-hosted gateway for connection to on-prem systems.
The gateway deployment on kubernetes went fine and the gateway registered in Azure. From the container's log, we can see the configuration was read correctly and a curl call to the backend system from kubernetes works too. Calling APIs over the gateway however does not work. We have the feeling this is caused by proxy settings. Our proxy server requires authentication and it seems to strand there. The propertie in kubernetes was set to avoid proxy for internal addressess but this doesn't seem to stick to the container. We still strand on the proxy authentication. Is there a way to configure the proxy settings in the container or is there a specific proxy configuration to stick to? We can't really whitelist the kubernetes host because it houses other services that would require the proxy wall to be up.

JayaC-MSFT 5,606 Reputation points

2020-09-08T09:30:36.22+00:00

@Anonymous Thank you for the question. I will check and update you at the earliest.
ChaitanyaNaykodi-MSFT 27,476 Reputation points Microsoft Employee Moderator

2020-09-11T05:01:11.157+00:00

Hello @Anonymous , Just following up here, to see if you were able to implement the solution provided below?
Bollaert, Igor 17 Reputation points

2020-09-24T07:00:32.95+00:00

Thanks for your reply. I was on vacation but will attempt to implement this asap and report back.

1 answer

Your answer

JayaC-MSFT 5,606 Reputation points

2020-09-08T09:30:36.22+00:00

@Anonymous Thank you for the question. I will check and update you at the earliest.
ChaitanyaNaykodi-MSFT 27,476 Reputation points Microsoft Employee Moderator

2020-09-11T05:01:11.157+00:00

Hello @Anonymous , Just following up here, to see if you were able to implement the solution provided below?
Bollaert, Igor 17 Reputation points

2020-09-24T07:00:32.95+00:00

Thanks for your reply. I was on vacation but will attempt to implement this asap and report back.

Answer 1

ChaitanyaNaykodi-MSFT 27,476 Microsoft Employee Moderator

Hello @Anonymous ,
After having a discussion with the internal product team. To route egress traffic from self-hosted gateway via a proxy you need to configure standard Linux environment variables HTTP_PROXY or HTTPS_PROXY with http://user:pass@hosting :port/ of the proxy.
Please let me know if the solution provided works or not, I will be glad to continue with our discussion.

Bollaert, Igor 17 Reputation points

2020-09-30T07:17:17.543+00:00

The HTTP_PROXY and HTTPS_PROXY variables were set to the kubernetes authentication proxy. The NO_PROXY variable was set to exclude our internal domains from the proxy.
These variables seem to work just fine with wget from the pod's shell but do not seem to honored by the gateway itself.
Wutzke Markus 21 Reputation points

2022-02-15T12:05:47.347+00:00

@Anonymous Did you find a solution to force the self-hosted gateway to do outgoing connectivity via your proxy?
Katta, Venkata 0 Reputation points

2023-08-03T18:33:47.44+00:00

I am also facing same issue. I am deploying a selfhosted gateway on on-prem and my gateway needs to talk with my proxy server with username and password for authorization and if that service account is valid then my gateway can talk to internet means Azure APIM. So I setup all environment variable what ever needed as HTTPS_PROXY HTTP_PROXY USERNAME PASSWORD as well but it still failing while connecting to my corporate proxy server. So need help on this scenario

Thanks in Advance

Share via

Azure APIM with self-hosted gateway

1 answer

Your answer