[2.14] OIDC PKCE Support (#2236)

* Add shared fle for OIDC Support for PKCE Extension

* Update OIDC pages

* Update shared-files/_oidc-pkce-support.md

Co-authored-by: Billy Tat <btat@suse.com>

* Reword OIDC PKCE support text

---------

Co-authored-by: Billy Tat <btat@suse.com>
This commit is contained in:
Lucas Saintarbor
2026-03-23 09:57:02 -07:00
committed by GitHub
co-authored by Billy Tat
parent 1870b57b6e
commit 4c23b0dd50
8 changed files with 30 additions and 0 deletions
@@ -53,6 +53,10 @@ if the user has not yet logged in to Rancher. However, if the user has previousl
| Client Secret | The generated Secret of your Amazon Cognito App Client. |
| Issuer | The Issuer URL of your Amazon Cognito App Client. It follows the format `https://cognito-idp.{region}.amazonaws.com/{userPoolId}`, and can be found in the App Client settings page. Rancher uses the Issuer URL to fetch all of the required URLs. |
## OIDC Support for PKCE Extension
<OIDCPKCESupport />
## Configuring OIDC Single Logout (SLO)
<ConfigureSLOOidc />
@@ -139,6 +139,10 @@ For example, if your IdP sends `groups` in a claim called `custom_roles`, enter
| Custom Email Claim | `email` | The name of the claim in the OIDC token that contains the user's email address. |
| Custom Groups Claim | `groups` | The name of the claim in the OIDC token that contains the user's group memberships (used for RBAC). |
## OIDC Support for PKCE Extension
<OIDCPKCESupport />
## Configuring OIDC Single Logout (SLO)
<ConfigureSLOOidc />
@@ -168,6 +168,10 @@ After configuration is completed, Rancher user permissions need to be reapplied
:::
## OIDC Support for PKCE Extension
<OIDCPKCESupport />
## Configuring OIDC Single Logout (SLO)
<ConfigureSLOOidc />
+3
View File
@@ -0,0 +1,3 @@
Rancher supports the Proof Key for Code Exchange (PKCE) extension (RFC 7636) for OIDC authentication providers. SHA-256 (`S256`) is the only supported PKCE verification method. To enable this feature, your authentication provider must use PKCE with `S256` for authorization requests.
You can enable this feature by selecting **Enable PKCE (S256)** in your authentication provider configuration in Rancher. Enabling `S256` PKCE token verification allows you to mitigate authorization code interception attacks during OIDC authentication flows.
+3
View File
@@ -16,6 +16,8 @@ import ConfigureSLOOidc from '/shared-files/_configure-slo-oidc.md';
import EOLRKE1Warning from '/shared-files/_eol-rke1-warning.md';
import PermissionsWarning from '/shared-files/_permissions-warning.md';
import SamlOpenLDAPGroupPermissions from '/shared-files/_saml-openldap-group-permissions.md';
import OIDCPKCESupport from '/shared-files/_oidc-pkce-support.md';
export default {
// Re-use the default mapping
@@ -37,4 +39,5 @@ export default {
EOLRKE1Warning,
PermissionsWarning,
SamlOpenLDAPGroupPermissions,
OIDCPKCESupport,
};
@@ -53,6 +53,10 @@ if the user has not yet logged in to Rancher. However, if the user has previousl
| Client Secret | The generated Secret of your Amazon Cognito App Client. |
| Issuer | The Issuer URL of your Amazon Cognito App Client. It follows the format `https://cognito-idp.{region}.amazonaws.com/{userPoolId}`, and can be found in the App Client settings page. Rancher uses the Issuer URL to fetch all of the required URLs. |
## OIDC Support for PKCE Extension
<OIDCPKCESupport />
## Configuring OIDC Single Logout (SLO)
<ConfigureSLOOidc />
@@ -139,6 +139,10 @@ For example, if your IdP sends `groups` in a claim called `custom_roles`, enter
| Custom Email Claim | `email` | The name of the claim in the OIDC token that contains the user's email address. |
| Custom Groups Claim | `groups` | The name of the claim in the OIDC token that contains the user's group memberships (used for RBAC). |
## OIDC Support for PKCE Extension
<OIDCPKCESupport />
## Configuring OIDC Single Logout (SLO)
<ConfigureSLOOidc />
@@ -168,6 +168,10 @@ After configuration is completed, Rancher user permissions need to be reapplied
:::
## OIDC Support for PKCE Extension
<OIDCPKCESupport />
## Configuring OIDC Single Logout (SLO)
<ConfigureSLOOidc />