From b325abf830463a5ae0148ec420b76af4381deae2 Mon Sep 17 00:00:00 2001 From: MofeLee Date: Mon, 17 Jul 2017 14:16:42 +0800 Subject: [PATCH] Update authentication.md --- docs/admin/authentication.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/authentication.md b/docs/admin/authentication.md index ffe4fd0e2b..2033b33206 100644 --- a/docs/admin/authentication.md +++ b/docs/admin/authentication.md @@ -277,7 +277,7 @@ solution for authentication. It does offer a few challenges: 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. 2. The `id_token` can't be revoked, its 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 -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` +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` #### Configuring the API Server