Skip to content

Commit 831833d

Browse files
islinwbchenopis
authored andcommitted
Update docs/admin/authentication.md (#5408)
* Update docs/admin/authentication.md * Update authentication.md
1 parent 82ac925 commit 831833d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/admin/authentication.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ with a value of `Basic BASE64ENCODED(USER:PASSWORD)`.
168168

169169
### Service Account Tokens
170170

171-
Service accounts are an automatically enabled authenticator that uses signed
171+
A service account is an automatically enabled authenticator that uses signed
172172
bearer tokens to verify requests. The plugin takes two optional flags:
173173

174174
* `--service-account-key-file` A file containing a PEM encoded key for signing bearer tokens.
@@ -281,8 +281,8 @@ Since all of the data needed to validate who you are is in the `id_token`, Kuber
281281
solution for authentication. It does offer a few challenges:
282282

283283
1. Kubernetes has no "web interface" to trigger the authentication process. There is no browser or interface to collect credentials which is why you need to authenticate to your identity provider first.
284-
2. The `id_token` can't be revoked, it's like a certificate so it should be short-lived (only a few minutes) so it can be very annoying to have to get a new token every few minutes
285-
3. There's no easy way to authenticate to the Kubernetes dashboard without using the `kubectl proxy` command or a reverse proxy that injects the `id_token`
284+
2. The `id_token` can't be revoked, it's like a certificate so it should be short-lived (only a few minutes) so it can be very annoying to have to get a new token every few minutes.
285+
3. There's no easy way to authenticate to the Kubernetes dashboard without using the `kubectl proxy` command or a reverse proxy that injects the `id_token`.
286286

287287

288288
#### Configuring the API Server
@@ -728,7 +728,7 @@ Finally, add the following parameters into API server start parameters:
728728

729729
./easyrsa --batch "--req-cn=${MASTER_IP}@`date +%s`" build-ca nopass
730730
1. Generate server certificate and key.
731-
(build-server-full [filename]: Generate a keypair and sign locally for a client or server)
731+
(build-server-full [filename]: Generate a keypair and sign locally for a client or server.)
732732

733733
./easyrsa --subject-alt-name="IP:${MASTER_IP}" build-server-full server nopass
734734
1. Copy `pki/ca.crt`, `pki/issued/server.crt`, and `pki/private/server.key` to your directory.
@@ -748,7 +748,7 @@ Finally, add the following parameters into API server start parameters:
748748
1. According to the ca.key generate a ca.crt (use -days to set the certificate effective time):
749749

750750
openssl req -x509 -new -nodes -key ca.key -subj "/CN=${MASTER_IP}" -days 10000 -out ca.crt
751-
1. Generate a server.key with 2048bit
751+
1. Generate a server.key with 2048bit:
752752

753753
openssl genrsa -out server.key 2048
754754
1. According to the server.key generate a server.csr:

0 commit comments

Comments
 (0)