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: docs/api/_index.md
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -199,7 +199,9 @@ Replace the TLS certificate and key on the fly. Reload is optional.
199
199
200
200
The certificates need to be base64 encoded as in the following example.
201
201
202
-
When updating the TLS certificate with a new certificate obtained by requesting a Certificate Signing Request (CSR) from the CSR Endpoint, the keydata field must be omitted. The certificate will only be updated if the public key associated with the new certificate matches the public key generated by the CSR Endpoint.
202
+
When updating the TLS certificate with a new certificate obtained by requesting a Certificate Signing Request (CSR) from
203
+
the CSR endpoint, the keydata field must be omitted. The certificate will only be updated if the public key associated
204
+
with the new certificate matches the public key generated by the CSR endpoint.
203
205
204
206
Example:
205
207
@@ -225,13 +227,15 @@ Example:
225
227
226
228
```bash
227
229
curl \
228
-
-u user:changeme \
229
-
-d '{"Country":"DE","State":"Bavaria","Locality":"Earth","Organization":"snclient","OrganizationalUnit":"IT","HostName":"Root CA SNClient", "NewKey":true, "KeyLength":4096}' \
230
-
https://127.0.0.1:8443/api/v1/admin/csr
230
+
-u user:changeme \
231
+
-d '{"Country":"DE","State":"Bavaria","Locality":"Earth","Organization":"snclient","OrganizationalUnit":"IT","HostName":"Root CA SNClient", "NewKey":true, "KeyLength":4096}' \
232
+
https://127.0.0.1:8443/api/v1/admin/csr
231
233
```
232
234
233
235
Returns PEM encoded csr
234
-
When NewKey:true is specified, a new private key will be generated and stored in a temporary file. This temporary file will be retained until you upload the signed certificate to the /api/v1/admin/certs/replace endpoint, at which point the new private key will be saved in the keyfile specified in the configuration
236
+
When NewKey:true is specified, a new private key will be generated and stored in a temporary file. This temporary file
237
+
will be retained until you upload the signed certificate to the /api/v1/admin/certs/replace endpoint, at which point the
238
+
new private key will be saved in the keyfile specified in the configuration
0 commit comments