Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v7] Document Okta OIDC provider workaround (#11948) #11999

Merged
merged 2 commits into from
Apr 15, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/pages/enterprise/sso.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -148,9 +148,9 @@ values to match your identity provider:
to the full [ADFS guide](./sso/adfs.mdx#create-teleport-roles) for details.
- `netiq` (OIDC): Used to enable NetIQ-specific ACR value processing; refer to
the [OIDC guide](./sso/oidc.mdx#optional-acr-values) for details.
- `ping` (SAML): Required for compatibility with Ping Identity (including
PingOne and PingFederate) when "Enforced Signed Authn Requests" is enabled in
the application settings.
- `ping` (SAML and OIDC): Required for compatibility with Ping Identity (including
PingOne and PingFederate).
- `okta` (OIDC): Required when using Okta as an OIDC provider.

At this time, the `spec.provider` field should not be set for any other identity providers.

Expand Down