Confirm Okta Identity Engine
Atomation's assessment supports Okta Identity Engine orgs only. Classic Engine orgs are not supported.
This is the assessment connection path. Customer portal SSO and SCIM are configured separately after your workspace is ready.
Atomation's assessment supports Okta Identity Engine orgs only. Classic Engine orgs are not supported.
During onboarding, Atomation provides the public key and setup instructions for an Okta API service app. Your team grants the read scopes used for inspection.
Atomation verifies token issuance and confirms the granted scopes before the first snapshot. No write scopes are requested for the assessment path.
The first scan captures an immutable snapshot, evaluates the rule library, and produces the initial report for review.
The customer portal can use Okta SSO and SCIM for team access. That integration is separate from the read-only service app that reviews your Okta org.
Repeat these steps for each additional Okta org under your main account. Atomation currently supports up to six orgs per account by default; higher limits can be approved by exception.
The read-only API service app lets Atomation assess your Okta configuration. SAML SSO and SCIM provision users into the Atomation customer portal. They serve different purposes and should be configured separately.
| Integration | Purpose | Guide |
|---|---|---|
| Read-only API service app | Lets Atomation inspect Okta configuration and produce the assessment report. | This page and onboarding instructions. |
| SAML SSO and SCIM | Lets your team sign in to the Atomation portal and keeps portal users in sync. | Open SSO/SCIM guide |
Once the first scan completes, review the findings, control mappings, and remediation sequence before making changes in Okta.
Read the report guideThe assessment, its security model, delivery options, and report format in more detail.
Book a free discovery call. We'll map your workflow, find the highest-value automation, and show you the smallest useful first build — no obligation.