Skip to content

Commit 8f2cf33

Browse files
authored
[zh] Update authentication.md (#32291)
* [zh] Update authentication.md Update authentication.md Sign off xin.li<[email protected]> * Update authentication.md
1 parent 94e0238 commit 8f2cf33

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

content/zh/docs/reference/access-authn-authz/authentication.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1145,7 +1145,7 @@ The following HTTP headers can be used to performing an impersonation request:
11451145

11461146
* `Impersonate-User`: The username to act as.
11471147
* `Impersonate-Group`: A group name to act as. Can be provided multiple times to set multiple groups. Optional. Requires "Impersonate-User".
1148-
* `Impersonate-Extra-( extra name )`: A dynamic header used to associate extra fields with the user. Optional. Requires "Impersonate-User". In order to be preserved consistently, `( extra name )` should be lower-case, and any characters which aren't [legal in HTTP header labels](https://tools.ietf.org/html/rfc7230#section-3.2.6) MUST be utf8 and [percent-encoded](https://tools.ietf.org/html/rfc3986#section-2.1).
1148+
* `Impersonate-Extra-( extra name )`: A dynamic header used to associate extra fields with the user. Optional. Requires "Impersonate-User". In order to be preserved consistently, `( extra name )` must be lower-case, and any characters which aren't [legal in HTTP header labels](https://tools.ietf.org/html/rfc7230#section-3.2.6) MUST be utf8 and [percent-encoded](https://tools.ietf.org/html/rfc3986#section-2.1).
11491149
* `Impersonate-Uid`: A unique identifier that represents the user being impersonated. Optional. Requires "Impersonate-User". Kubernetes does not impose any format requirements on this string.
11501150
-->
11511151
以下 HTTP 头部字段可用来执行伪装请求:
@@ -1841,15 +1841,18 @@ Certificates)。
18411841

18421842
<!--
18431843
Optionally, the response can include the expiry of the credential formatted as a
1844-
RFC3339 timestamp. Presence or absence of an expiry has the following impact:
1844+
[RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) timestamp.
1845+
Presence or absence of an expiry has the following impact:
18451846

18461847
- If an expiry is included, the bearer token and TLS credentials are cached until
18471848
the expiry time is reached, or if the server responds with a 401 HTTP status code,
18481849
or when the process exits.
18491850
- If an expiry is omitted, the bearer token and TLS credentials are cached until
18501851
the server responds with a 401 HTTP status code or until the process exits.
18511852
-->
1852-
作为一种可选方案,响应中还可以包含以 RFC3339 时间戳格式给出的证书到期时间。
1853+
作为一种可选方案,响应中还可以包含以
1854+
[RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339)
1855+
时间戳格式给出的证书到期时间。
18531856
证书到期时间的有无会有如下影响:
18541857

18551858
- 如果响应中包含了到期时间,持有者令牌和 TLS 凭据会被缓存,直到到期期限到来、

0 commit comments

Comments
 (0)