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
Add support for specifying client TLS key/cert in json-based config (#41)
* Add support for specifying client TLS key/cert in json-based config
Includes updates to EtcdClient/EtcdClusterConfig to ensure that
cached/shared client instances are appropriately reference counted.
* Fix PersistentLeaseKeyTest timing flake
Copy file name to clipboardExpand all lines: etcd-json-schema.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,15 +9,18 @@ Example JSON config doc:
9
9
"password": "password",
10
10
"root_prefix": "aka-chroot-or-namespace",
11
11
"certificate_file": "etcd-dev.pem",
12
-
"override_authority": "etcd-development-01"
12
+
"override_authority": "etcd-development-01",
13
+
"client_key_file": "etcd-client-key.key",
14
+
"client_certificate_file": "etcd-client-cert.crt"
13
15
}
14
16
```
15
17
16
18
- All attributes apart from `endpoints` are optional.
17
19
- The `root_prefix` attribute currently has **no effect** on clients created via `EtcdClientConfig.getClient()`. It's included in the configuration for use by application code (to query via `EtcdClientConfig.getRootPrefix()`). In future full chroot-like functionality at the client level might be supported.
18
20
-`certificate_file` is the name of a pem-format (public) cert to use for TLS server-auth, either an absolute path or a filename assumed to be in the same directory as the json config file itself.
19
21
- A `certificate` attribute may be included _instead of_`certificate_file`, whose value is an embedded string UTF-8 pem format certificate. This allows a single json doc to hold all of the necessary connection info.
20
-
- The `override_authority` is optional and may be used to override the authority used for TLS hostname verification for _all_ endpoints.
22
+
-`client_key_file` and `client_certificate_file` form an optional key/cert pair for TLS client-auth. Either may also be embedded in a similar way by instead including `client_key` and/or `client_certificate` string attributes.
23
+
- The `override_authority` attribute is optional and may be used to override the authority used for TLS hostname verification for _all_ endpoints.
0 commit comments