The Okta Workforce integration enables Single Sign-On (SSO) for your organization’s employees accessing Cora.ai. Once configured, employees authenticate using their existing corporate credentials through Okta — no separate Cora.ai password required. Setup involves creating an OIDC app in Okta and sharing the credentials securely with the Cora.ai team, who complete the backend configuration.Documentation Index
Fetch the complete documentation index at: https://docs.cora.ai/llms.txt
Use this file to discover all available pages before exploring further.
| Detail | Value |
|---|---|
| Integration type | OpenID Connect (OIDC), Organization-Level |
| Setup time | 10–15 minutes |
| Required role | Okta Administrator |
Prerequisites
- An active Okta Workforce Identity subscription
- Administrator access in your Okta organization
- Your organization’s email domain(s) (e.g.,
yourcompany.com)
How authentication works
Once the integration is active, Cora.ai automatically routes your employees to Okta based on their email domain:- The employee enters their work email (e.g.,
john@yourcompany.com). - Cora.ai detects the domain and routes the login request to Okta.
- The employee authenticates via Okta, including MFA if configured.
- Upon successful authentication, the employee is logged into Cora.ai.
Benefits
- Seamless user experience — Employees use their existing corporate credentials.
- Centralized access control — Manage Cora.ai access through Okta policies and groups.
- Enhanced security — Leverage Okta’s MFA and adaptive authentication.
- Zero code changes — The integration is transparent to end users.
- Audit & compliance — All authentication events are captured in Okta’s centralized audit logs.
Setup
Create an Okta OIDC app integration
For full details on creating OIDC app integrations, see Create OIDC app integrations in the Okta Help Center.Create the app:
Under Assignments, choose who can access the application. Start with specific groups for pilot testing before rolling out organization-wide.Click Save.Save your credentials:After saving, open the application details page and copy the following values — you’ll need them in Step 2:
- Log into the Okta Admin Console as an Administrator.
- Navigate to Applications → Applications.
- Click Create App Integration.
- Set Sign-in method to OIDC - OpenID Connect.
- Set Application type to Web Application.
- Click Next.
| Setting | Value |
|---|---|
| App integration name | Cora.ai (or your preferred name) |
| Grant type | Authorization Code (selected by default) |
| Sign-in redirect URIs | https://auth.cora.ai/login/callback |
| Sign-out redirect URIs | Leave blank (optional) |
| Trusted Origins | https://cora.ai/ |
- Okta Domain — Your organization’s Okta domain (e.g.,
yourcompany.okta.com) - Client ID — Copy this value from the app details page
- Client Secret — Click Show, then copy the value
Share credentials securely with Cora.ai
Once you’ve created the Okta application, send the credentials to Cora.ai so the team can complete the backend configuration.Required information:
Recommended: share via Bitwarden SendBitwarden Send is a secure one-time sharing tool — no Bitwarden account is required to use it.
| Field | Description |
|---|---|
| Okta Domain | Your organization’s Okta domain (e.g., yourcompany.okta.com) |
| Client ID | Unique identifier for the Okta app you created in Step 1 |
| Client Secret | Authentication secret for the Okta app from Step 1 |
| Email Domain(s) | Your organization’s email domain(s) for automatic routing (e.g., yourcompany.com) |
- Go to bitwarden.com/products/send.
- In the Text tab, paste the following, filling in your values:
- Click Create Send.
- Click Copy Link.
- Send the link to your Cora.ai contact via email or Slack.
- Share via your organization’s secure file-sharing platform
- Send via encrypted email
- Share during a scheduled call with screen sharing
- The Cora.ai team receives your credentials securely.
- The backend integration is configured — typically within 1 business day.
- You’ll receive a notification when the integration is ready for testing.
- Test the integration with your pilot users before rolling it out organization-wide.
