From 722b88c6143b0fe1fa34a951ec9fcd4658d806ff Mon Sep 17 00:00:00 2001 From: Kaitlyn Barnard Date: Mon, 24 Sep 2018 19:57:56 -0700 Subject: [PATCH] updating Okta reference (#10378) --- content/en/docs/reference/access-authn-authz/authentication.md | 2 +- 1 file changed, 1 insertion(+), 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 0ef41c918f..bfd4e2c273 100644 --- a/content/en/docs/reference/access-authn-authz/authentication.md +++ b/content/en/docs/reference/access-authn-authz/authentication.md @@ -342,7 +342,7 @@ Setup instructions for specific systems: The first option is to use the kubectl `oidc` authenticator, which sets the `id_token` as a bearer token for all requests and refreshes the token once it expires. After you've logged into your provider, use kubectl to add your `id_token`, `refresh_token`, `client_id`, and `client_secret` to configure the plugin. -Providers that don't return an `id_token` as part of their refresh token response (e.g. [Okta](https://developer.okta.com/docs/api/resources/oidc.html#response-parameters-4)) aren't supported by this plugin and should use "Option 2" below. +Providers that don't return an `id_token` as part of their refresh token response aren't supported by this plugin and should use "Option 2" below. ```bash kubectl config set-credentials USER_NAME \