Okta identity integration with GenticFlow
Okta OIDC sign-in for client portal and agent chat sessions
GenticFlow supports Okta as an OIDC authentication provider. Admins configure an Okta web application, client ID, client secret, Okta issuer URL, scopes, claim mapping, and organization assignments so users can authenticate through Okta where the product uses OIDC sign-in.
What You Get
OIDC Authentication Provider
- Okta is a supported authentication provider type
- Issuer URL can use an Okta domain or the default authorization server path
- Authorization code with PKCE is used for OIDC sessions
- Scopes default to openid, email, and profile
Endpoint Discovery and Claims
- OIDC endpoints can be auto-discovered from the issuer URL
- Authorization, token, userinfo, JWKS, and end-session endpoints can be stored
- Email and name claims are configurable
- Organizations can be assigned to the provider
Password Reset Link Support
- Okta password reset can be exposed as a provider-specific reset link
- Generic custom reset URLs are also supported for OIDC providers
- This Okta page covers OIDC sign-in rather than Okta directory sync
- Okta remains the identity provider and access policy authority
How It Works
Create an Okta OIDC web app
Configure authorization code flow, redirect URI, assignments, and required scopes in Okta.
Add Okta provider settings
Enter the client ID, client secret, Okta domain or issuer URL, scopes, and claim mapping.
Discover OIDC endpoints
GenticFlow can discover the provider endpoints from the issuer URL.
Assign organizations
Connect the Okta provider to the organizations that should use it for supported OIDC sign-in flows.
Identity context for support workflows.
Okta remains the identity provider or directory source. GenticFlow uses supported identity sync and OIDC sign-in flows to connect users, organizations, and sessions to the service desk workflow.
See It In Action