Allow configuring the value for httpOptions.rejectUnauthorized via Environment variables about unleash-proxy HOT 6 CLOSED

Hi @vkbandi - Thanks for opening this issue! I'll reach out to the rest of the team and we'll get back to you 👍

from unleash-proxy.

from unleash-proxy.

Hi, I all node.js applications you can allow any self-signed certificates by setting the environment variable NODE_TLS_REJECT_UNAUTHORIZED=0 (see official node.js docs).

How you would do this with docker then would be:

docker run \
   -e NODE_TLS_REJECT_UNAUTHORIZED=0 \
   -e UNLEASH_PROXY_CLIENT_KEYS=some-secret \
   -e UNLEASH_URL=https://app.unleash-hosted.com/demo/api/ \
   -e UNLEASH_API_TOKEN=56907a2fa53c1d16101d509a10b78e36190b0f918d9f122d \
   -p 3000:3000 \
   unleashorg/unleash-proxy

from unleash-proxy.

Hi @ivarconr Thanks for replying, I tried with setting NODE_TLS_REJECT_UNAUTHORIZED=0 in docker environment variables and also by creating a node js application to act as unleash proxy, but it never worked. Maybe Im missing something her.

But the only config that worked is setting the httpOptions: { rejectUnauthorized: false } in the node js application.

from unleash-proxy.

I see. Maybe we need to support that as a configurable option then. Do you mind looking in to a PR?

from unleash-proxy.

Sorry for the delay, need few more days to work on this

from unleash-proxy.