You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 8, 2022. It is now read-only.
Snap supports TLS for GRPC plugins. Referring to [secure plugin communication](https://github.com/intelsdi-x/snap/blob/master/docs/SECURE_PLUGIN_COMMUNICATION.md) for details. How to setup TLS on both server and client? The [Setup TLS Certificates](https://github.com/intelsdi-x/snap/blob/master/docs/SETUP_TLS_CERTIFICATES.md) has everything.
307
307
308
-
#### Sample Use Cases
308
+
#### Examples
309
309
310
-
Here is a list of good and bad command use cases.
310
+
##### Definition of flags
311
311
312
312
| Flag | Description |
313
313
| ------ | ------ |
314
-
| tls-cert | TLS client certificate |
315
-
| tls-key | TLS client private key |
316
-
| ca-cert-paths | TLS client CA certificates |
317
314
| plugin-cert | TLS server certificate |
318
315
| plugin-key | TLS server private key |
319
316
| plugin-ca-certs | TLS server CA certificates |
320
317
321
-
##### Case 1: Start `snapteld` with TLS certs
318
+
##### Starting `snapteld`
322
319
323
320
Snap is a client for all GRPC plugins. Note that Snap loads CA certificates from your OS certificate trust store if it's not specified.
> :collision: Urgh! HTTPS does not have a trusted CA. There is no way to specify a CA using a flag forHTTPS currently. Putting the trusted CAin your OS trust store in production. Using --insecure flag for your testing convenience.
0 commit comments