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

Clarify caching of exec auth tokens (#7881)

Browse Source 
* Clarify caching of exec auth tokens

* Update the wording
This commit is contained in:
Rajat Jindal
2018-03-28 11:41:04 -07:00
committed by k8s-ci-robot
parent fbafe499d2
commit bf45a16314
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/admin/authentication.md
+2 -1
View File
@@ -828,7 +828,8 @@ Kubernetes API.
Optionally, this output can include the expiry of the token formatted as a RFC3339 timestamp. Optionally, this output can include the expiry of the token formatted as a RFC3339 timestamp.
If an expiry is omitted, the bearer token is cached until the server responds with a 401 HTTP If an expiry is omitted, the bearer token is cached until the server responds with a 401 HTTP
status code. status code. Note that this caching is only for the duration of process and therefore the plugin
is triggered each time the tool using the plugin is invoked.
```json ```json
{ {