djpbessems/ContainerImage.Pinniped
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md

Browse Source 
Co-authored-by: Ryan Richard <rrichard@pivotal.io>
This commit is contained in:
anjalitelang 2022-01-20 10:42:49 -05:00 committed by GitHub
parent d21012d39c
commit 3895312b0f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
site/content/posts/2022-01-18-idp-refresh-tls-ciphers-for-compliance.md
View File

@ -25,7 +25,7 @@ A critical compliance use case that many organizations have to meet is to ensure
### OIDC Identity Provider triggered refreshes
Supporting OIDC IDP refreshes will require certain changes to the OIDCIdentityProvider resource on the cluster. These changes depend mostly on how your OIDC IDP handles refresh tokens. In general, your IDP will either honor sending refresh tokens or not. Let’s look at what changes are needed in the IDP configuration for when refresh tokens are supported and when they are not:
Supporting OIDC IDP refreshes will require certain changes to the OIDCIdentityProvider resource on the cluster. These changes depend mostly on how your OIDC IDP handles refresh tokens. In general, your IDP will either honor sending refresh tokens or not. Let’s look at what changes are needed in the IDP configuration for when refresh tokens are supported and when they are not supported.
#### When your OIDC IDP can return refresh tokens (Preferred approach)