Add support for skipping TLS certificate verification #54
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.
CrowdSec now allows automatic agent registration if mutual-TLS is activated on the LAPI server/instance. This will probably be the most common way Kubernetes deployments of CrowdSec will operate.
However, when TLS mode is activated on the LAPI server, most of the time it will be using self-signed certificates. In this Traefik CrowdSec bouncer, it's possible to change the scheme from
http
tohttps
, but certificate verification will fail with self-signed certificates. This PR adds an environment variable to allow one to deactivate certificate verification.