Skip to content

Commit bd86fd6

Browse files
committed
Clarifications
1 parent 9333f62 commit bd86fd6

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

step-ca/templates.mdx

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Configuring `step-ca` Templates
33
html_title: Configuring open source step-ca Templates
44
description: Learn how to configure step-ca Templates
5-
updated_at: March 24, 2024
5+
updated_at: March 25, 2025
66
---
77

88
People use private CAs for all sorts of things, in many different contexts:
@@ -222,16 +222,14 @@ Here are some constants available in X.509 certificate templates:
222222
- **.Subject**:
223223
The subject that was passed in to `step certificate` or `step ca certificate`. Specifically,
224224
`.Subject.CommonName` contains the Common Name for the certificate. By default, a passed-in subject
225-
value must match a value from a trusted source in order to be added to the certificate. The
226-
client is only a trusted source if they are an admin using the JWK provisioner.
225+
value must match a value from a trusted source in order to be added to the certificate.
227226

228227
- **.SANs**:
229228
Subject Alternative Names.
230229
This is a list of maps containing SANs for the certificate.
231230
Unless SANs are specified (using the `--san` flag, for example),
232231
the `.Subject.CommonName` is the default SAN. By default, a passed-in subject
233-
value must match a value from a trusted source in order to be added to the certificate. The
234-
client is only a trusted source if they are an admin using the JWK provisioner.
232+
value must match a value from a trusted source in order to be added to the certificate.
235233

236234
- **.Token**:
237235
If a signed token was used to obtain the certificate

0 commit comments

Comments
 (0)