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

fixed some grammatical mistakes

Browse Source
This commit is contained in:
sahadat_hossain
2021-02-12 16:57:50 +06:00
parent 2c942aeb79
commit c0770869ff
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/access-authn-authz/authentication.md
+4 -4
View File
@@ -205,7 +205,7 @@ spec:
``` ```
Service account bearer tokens are perfectly valid to use outside the cluster and Service account bearer tokens are perfectly valid to use outside the cluster and
can be used to create identities for long standing jobs that wish to talk to the can be used to create identities for long-standing jobs that wish to talk to the
Kubernetes API. To manually create a service account, simply use the `kubectl Kubernetes API. To manually create a service account, simply use the `kubectl
create serviceaccount (NAME)` command. This creates a service account in the create serviceaccount (NAME)` command. This creates a service account in the
current namespace and an associated secret. current namespace and an associated secret.
@@ -233,7 +233,7 @@ secrets:
- name: jenkins-token-1yvwg - name: jenkins-token-1yvwg
``` ```
The created secret holds the public CA of the API server and a signed JSON Web The created secret holds the public CA of the API server, and a signed JSON Web
Token (JWT). Token (JWT).
```bash ```bash
@@ -320,7 +320,7 @@ sequenceDiagram
8. Once authorized the API server returns a response to `kubectl` 8. Once authorized the API server returns a response to `kubectl`
9. `kubectl` provides feedback to the user 9. `kubectl` provides feedback to the user
Since all of the data needed to validate who you are is in the `id_token`, Kubernetes doesn't need to Since all the data needed to validate who you are is in the `id_token`, Kubernetes doesn't need to
"phone home" to the identity provider. In a model where every request is stateless this provides a very scalable "phone home" to the identity provider. In a model where every request is stateless this provides a very scalable
solution for authentication. It does offer a few challenges: solution for authentication. It does offer a few challenges:
@@ -733,7 +733,7 @@ to the impersonated user info.
The following HTTP headers can be used to performing an impersonation request: The following HTTP headers can be used to performing an impersonation request:
* `Impersonate-User`: The username to act as. * `Impersonate-User`: The username to act as.
* `Impersonate-Group`: A group name to act as. Can be provided multiple times to set multiple groups. Optional. Requires "Impersonate-User" * `Impersonate-Group`: A group name to act as. Can be provided multiple times to set multiple groups. Optional. Requires "Impersonate-User".
* `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). * `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).
{{< note >}} {{< note >}}