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
- Nodes certificates validity period is no longer hardcoded and must instead be set by operators and renewed by members (#2924):
1251
-
1252
1259
- The new `node_certificate.initial_validity_days` (defaults to 1 day) configuration entry lets operators set the initial validity period for the node certificate (valid from the current system time).
1253
1260
- The new `command.start.service_configuration.maximum_node_certificate_validity_days` (defaults to 365 days) configuration entry sets the maximum validity period allowed for node certificates.
1254
1261
- The new `set_node_certificate_validity` proposal action allows members to renew a node certificate (or `set_all_nodes_certificate_validity` equivalent action to renew _all_ trusted nodes certificates).
1255
1262
1256
1263
- Service certificate validity period is no longer hardcoded and must instead be set by operators and renewed by members (#3363):
1257
-
1258
1264
- The new `service_certificate_initial_validity_days` (defaults to 1 day) configuration entry lets operators set the initial validity period for the service certificate (valid from the current system time).
1259
1265
- The new `maximum_service_certificate_validity_days` (defaults to 365 days) configuration entry sets the maximum validity period allowed for service certificate.
1260
1266
- The new `set_service_certificate_validity` proposal action allows members to renew the service certificate.
@@ -1535,13 +1541,11 @@ Key-Value Store
1535
1541
#### Certificate(s) Validity Period
1536
1542
1537
1543
- Nodes certificates validity period is no longer hardcoded and must instead be set by operators and renewed by members (#2924):
1538
-
1539
1544
- The new `node_certificate.initial_validity_days` (defaults to 1 day) configuration entry lets operators set the initial validity period for the node certificate (valid from the current system time).
1540
1545
- The new `command.start.service_configuration.maximum_node_certificate_validity_days` (defaults to 365 days) configuration entry sets the maximum validity period allowed for node certificates.
1541
1546
- The new `set_node_certificate_validity` proposal action allows members to renew a node certificate (or `set_all_nodes_certificate_validity` equivalent action to renew _all_ trusted nodes certificates).
1542
1547
1543
1548
- Service certificate validity period is no longer hardcoded and must instead be set by operators and renewed by members (#3363):
1544
-
1545
1549
- The new `service_certificate_initial_validity_days` (defaults to 1 day) configuration entry lets operators set the initial validity period for the service certificate (valid from the current system time).
1546
1550
- The new `maximum_service_certificate_validity_days` (defaults to 365 days) configuration entry sets the maximum validity period allowed for service certificate.
1547
1551
- The new `set_service_certificate_validity` proposal action allows members to renew the service certificate.
@@ -2284,17 +2288,14 @@ The 1.0 release will require minimal changes from this release.
2284
2288
### Added
2285
2289
2286
2290
- Experimental
2287
-
2288
2291
- New CCF nodes can now join from a [snapshot](https://microsoft.github.io/CCF/ccf-0.13.0/operators/start_network.html#resuming-from-existing-snapshot) (#1500, #1532)
2289
2292
- New KV maps can now be created dynamically in a transaction (#1507, #1528)
2290
2293
2291
2294
- CLI
2292
-
2293
2295
- Subject Name and Subject Alternative Names for the node certificates can now be passed to cchost using the --sn and --san CLI switches (#1537)
2294
2296
- Signature and ledger splitting [flags](https://microsoft.github.io/CCF/ccf-0.13.0/operators/start_network.html#signature-interval) have been renamed more accurately (#1534)
2295
2297
2296
2298
- Governance
2297
-
2298
2299
-`user_data` can be set at user creation, as well as later (#1488)
0 commit comments