Pull users, groups and group memberships from your Okta org.
Source connector — pulls identity and access data from Okta into ComplianceScout where it is scored against your compliance frameworks and violation rules.
After a successful sync, the following data is available in your ComplianceScout dashboard for violation detection and reporting.
These fields are collected when you add the connector in the ComplianceScout dashboard. Secrets are encrypted at rest using AES-256-GCM and are never logged.
| Field | Type | Required | Notes |
|---|---|---|---|
| Org subdomain | Text | Required | The part before the domain — e.g. "acme" for acme.okta.com |
| Domain | Select | Required | Options: okta.com · okta-gov.com · okta.mil |
| API token | Secret | Required | Create a read-only API token under Security → API in the Okta Admin Console. |
Follow these steps to gather the credentials above and connect Okta to ComplianceScout.
Log in to your Okta Admin Console and navigate to Security → API in the left sidebar.
Click Tokens → Create Token. Name it "ComplianceScout" and copy the token value immediately — it is shown only once.
In ComplianceScout, go to Data & Secrets → Integrations → Add Connector → Okta, enter your org subdomain (e.g. "acme"), select your domain suffix (okta.com, okta-gov.com, or okta.mil), and paste the API token.
Click Test Connection to verify, then Save.
Start a free trial — your tenant is provisioned instantly and you can wire up this integration from the connectors page.