Skip to content

Commit 076c879

Browse files
raesenetengqm
andauthored
Update content/en/docs/concepts/security/hardening-guide/authentication-mechanisms.md
Co-authored-by: Qiming Teng <[email protected]>
1 parent 0761ef8 commit 076c879

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/en/docs/concepts/security/hardening-guide/authentication-mechanisms.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,8 +35,8 @@ While this mechanism can also be used for user authentication, it might not be s
3535
production use due to several restrictions:
3636

3737
- Client certificates cannot be individually revoked. Once compromised, a certificate can be used
38-
by an attacker until it expires. To mitigate this risk, it is recommended to configure short
39-
lifetimes for user authentication credentials created using client certificates.
38+
by an attacker until it expires. To mitigate this risk, it is recommended to configure short
39+
lifetimes for user authentication credentials created using client certificates.
4040
- If a certificate needs to be invalidated, the certificate authority must be re-keyed, which
4141
can introduce availability risks to the cluster.
4242
- There is no permanent record of client certificates created in the cluster. Therefore, all

0 commit comments

Comments
 (0)