Add optional insecure flag for self-signed certificates in script #41
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.
Add support for insecure flag in installation script
Add optional --insecure.
Pass -insecure to rmmagent for both initial install and the systemd service (ExecStart).
Add --no-check-certificate to wget when fetching MeshAgent.
Update help output to document the flag.
Example:
./rmmagent-linux.sh install "<mesh_url>" "<api_url>" <client_id> <site_id> "<auth_key>" server --insecure
Omit --insecure to retain default secure behavior.
Compatibility
Backwards compatible: default behavior unchanged when the flag is not supplied.
##Testing
Verified install with and without --insecure.
Confirmed: self-signed cert scenarios no longer block API enrollment or MeshAgent download.
Confirmed: rerunning installer no longer errors on existing mesh directory or missing temp files.