whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve --requestheader-client-ca-file warning (#10093)

Browse Source 
It's important to use a distinct CA (unless you exactly know what you
are doing) but not clear from the current documentation and warning.
This commit is contained in:
Michael Schubert
2018-09-06 08:55:13 +02:00
committed by k8s-ci-robot
parent 9ff4313339
commit 949a1ff541
3 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/access-authn-authz/authentication.md
+2 -1
View File
@@ -548,7 +548,8 @@ extra:
In order to prevent header spoofing, the authenticating proxy is required to present a valid client
certificate to the API server for validation against the specified CA before the request headers are
checked.
checked. WARNING: do **not** reuse a CA that is used in a different context unless you understand
the risks and the mechanisms to protect the CA's usage.
* `--requestheader-client-ca-file` Required. PEM-encoded certificate bundle. A valid client certificate must be presented and validated against the certificate authorities in the specified file before the request headers are checked for user names.
* `--requestheader-allowed-names` Optional. List of common names (cn). If set, a valid client certificate with a Common Name (cn) in the specified list must be presented before the request headers are checked for user names. If empty, any Common Name is allowed.