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
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@ The most important part of the config is this section
66
66
67
67
`ca_url` : ACME directory URL of external certificate authority. To get signed certs from InCommon use `https://acme.sectigo.com/v2/InCommonRSAOV`
68
68
69
-
Many commercial certificate authorities support ACME over external account binding (EAB). You will need to create an EAB token to get HMAC Key and Key ID related to your account.
69
+
Most commercial certificate authorities (such as Sectigo) support ACME over external account binding (EAB). You will need to to get your EAB credentials i.e HMAC Key and Key ID related to your account.
70
70
71
71
```json
72
72
"account_email": "admin@example.com",
@@ -76,7 +76,7 @@ Many commercial certificate authorities support ACME over external account bindi
76
76
77
77
### Starting the ACME server
78
78
79
-
Upon starting the ACME server it automatically obtains a SSL/TLS certificate from InCommon for itself
79
+
Upon starting the ACME server it automatically obtains a SSL/TLS certificate for itself.
80
80
81
81
```sh
82
82
$ ./step-ca ca.json
@@ -192,7 +192,7 @@ We have our certificate signed by InCommon 🎉
192
192
193
193
### Renewing a certificate
194
194
195
-
Issuing a certificate is _generally_ not a problem. It's the ability to renew a certificate and reload services post renewal and doing so in a consistent and reliable way is usually the problem. The certificate we obtained above has validity for 13 months! I am using the `--force` flag for renewal only because the default configuration in ACME clients only performs automatic renewal `1 < N < 30` number of days before certificate expiration. This default behaviour can be changed if needed, I think.
195
+
Issuing a certificate is _generally_ not a problem in enterprise environments. But the ability to reliably renew certificates and reload services gracefully post renewal is. I am using the `--force` flag for renewal only because the default configuration in ACME clients only performs automatic renewal `1 < N < 30` number of days before certificate expiration.
0 commit comments