This repository has been archived by the owner on Sep 3, 2024. It is now read-only.
Close #10 Added warning that appears if insecureSkipTlsVerify is true #14
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a special flag in the config for Openshift Client -
insecureSkipTlsVerify
. A true value means that if the authenticity of the certificate is not established, then the execution will continue anyway (regardless of the type of certificate, self-signed or not). Also, it depends onprocess.env.NODE_TLS_REJECT_UNAUTHORIZED
. So for enablinginsecureSkipTlsVerify
process.env.NODE_TLS_REJECT_UNAUTHORIZED
must be"0"
. Also, I've addedlogger.warn
in the Client forinsecureSkipTlsVerify
true value. @aiwilliams, can you comment this? I think the problem is the wrong value of param. Will you have enoughlogger.warn
call from our side for generating warn in UI? Or maybe we need to call another method?