-
Notifications
You must be signed in to change notification settings - Fork 149
Option to ignore tls certs (self signed) #12
Comments
Thanks for the request @vijaybandari. I'm currently looking into how to do this via the HTTP API and will get it out soon. |
Looked at the npm module (axios) you are using and here is the flag to skip tls verification.
Locally tested it by adding the above line to login.js and it worked fine. Will try to implementing it properly (node is not my cup of tea, but will give a try) :) |
Gotcha, it actually rejects on Axios (node), makes sense! Definitely feel free to submit a PR, otherwise we can implement it soon. |
@vijaybandari I was thinking about this and I don't think this is something that should be done through the UI. This is because the UI that you are loading to can serve multiple clients. If you were to change the node environment with I believe the best way to enable this is through the docker run by specifying Can you try running vault-ui with docker run -d \
-p 8000:8000 \
-e NODE_TLS_REJECT_UNAUTHORIZED=0 \
--name vault-ui \
djenriquez/vault-ui and tell me if that works? |
It didn't work. I think this sets environment variable at system level (docker) & not accessible by node. |
Ok, I'll look into a commander argument for running vault-ui with the necessary flag. Just to clarify, you said adding |
yes DJ |
You added this to login.js? |
Yes. |
@djenriquez Wait, I think it's working. Not sure why it didn't work earlier. I will test it completly, give me sometime. |
It's weird, it didn't work earlier (was using 4 days old docker image). Could be my docker setup issue, today docker itself stopped working and have to reset and pull latest image and works perfectly fine. Thank you very much for your help. |
Reference commit 5c215f4e. Closing, thanks for helping get this set up @vijaybandari! |
No description provided.
The text was updated successfully, but these errors were encountered: