From ae43738785e7e082d876dc7ad63432379d7151ff Mon Sep 17 00:00:00 2001 From: anjalitelang <49958114+anjaltelang@users.noreply.github.com> Date: Thu, 20 Jan 2022 10:43:27 -0500 Subject: [PATCH] Update site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md Co-authored-by: Ryan Richard --- .../posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md b/site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md index fb48a72a..9d1deda4 100644 --- a/site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md +++ b/site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md @@ -35,7 +35,7 @@ Note that before this release, the default value of additionalScopes was only "o **If you are an Existing Pinniped OIDC user upgrading to this version,** you may need to update the additionalScopes and additionalAuthorizeParameters in your pre-existing installation of the Pinniped Supervisor **before upgrading to this version** so that there is seamless upgrade experience for your end users accessing the cluster. You may also need to update the settings on your OIDC client in the UI or API of your IDP to allow the client to perform *refresh grants*. Please see below for an example using Okta. -Example changes to Okta OIDCProvider CRD: +Example Okta OIDCProvider CR with updated additionalScopes setting: ```yaml apiVersion: idp.supervisor.pinniped.dev/v1alpha1