From a45bf8459dc0c44ef37642581e8ddc699df4ef8e Mon Sep 17 00:00:00 2001 From: Shubham Date: Wed, 23 Feb 2022 12:24:18 +0530 Subject: [PATCH] Added Hyperlink to RFC3339. (#31836) * Added Hyperlink to RFC3339. * Wrapping a line! --- .../en/docs/reference/access-authn-authz/authentication.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/docs/reference/access-authn-authz/authentication.md b/content/en/docs/reference/access-authn-authz/authentication.md index a7d5cd84d9..30e1725859 100644 --- a/content/en/docs/reference/access-authn-authz/authentication.md +++ b/content/en/docs/reference/access-authn-authz/authentication.md @@ -1144,7 +1144,9 @@ If specified, `clientKeyData` and `clientCertificateData` must both must be pres {{< /tabs >}} Optionally, the response can include the expiry of the credential formatted as a -RFC3339 timestamp. Presence or absence of an expiry has the following impact: +[RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) timestamp. + +Presence or absence of an expiry has the following impact: - If an expiry is included, the bearer token and TLS credentials are cached until the expiry time is reached, or if the server responds with a 401 HTTP status code,