Studio Project workflows for Okta entitlements, entitlement bundles, grants, and access certification campaigns
Okta is a cloud identity platform providing single sign-on, multi-factor authentication, lifecycle management, and identity governance for workforce and customer identities. This project covers Okta's Identity Governance API — entitlements, access grants, resource collections, access certification campaigns, access requests, and continuous security access reviews.
This project provides OpenAPI specs for automating against Okta's Identity Governance REST API via an Integration Model. The -latest spec is a curated subset covering common CRUD for governance automation — see OpenAPIs below.
| Asset | Description |
|---|---|
| OpenAPIs/ | Okta Identity Governance REST API OpenAPI specs — curated -latest plus the full dated spec |
| Studio Projects/Okta Management | 29 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Okta Identity Governance | 3.2.0 |
| Okta Management Integration Model | Required to build automation against the OpenAPI specs |
Import the OpenAPI spec from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at your Okta org.
Authentication is an API token in the Authorization header, using the SSWS token format:
Authorization: SSWS <your-okta-api-token> Generate a token in the Okta Admin Console under Security → API → Tokens.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"ApiKey": {
"value": "<your-api-key>"
}
},
"server": {
"protocol": "https",
"host": "subdomain.okta.com",
"base_path": ""
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
okta_management-latest.json | latest (curated) | 65 | Trimmed to 65 of 162 upstream operations — see breakdown below |
okta_management-3.2.0.json | 3.2.0 | 162 | Full spec for Okta Identity Governance 3.2.0 (162 operations). |
okta_management-latest.jsonActively-maintained spec (x-vendor-api-version: 3.2.0). Trimmed to 65 of 162 upstream operations covering common CRUD for automation. The full upstream spec is Okta's Identity Governance API in its entirety; excluded areas are admin-configuration surfaces (request types, request conditions/sequences/settings, entitlement settings, org and certification settings, resource owners), risk scoring (risk rules and risk-rule assessments), job/task-queue polling, and personal ("my") self-service endpoints that duplicate an equivalent admin-level operation already covered.
Resources included, by category:
okta_management-3.2.0.jsonFull, unmodified vendor spec for Okta Identity Governance 3.2.0 (162 operations) — the vendor's complete API surface, preserved as-is. See okta_management-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Okta Management:latest Integration Model (see okta_management-latest.json above). The project contains 29 workflows organized into 6 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Entitlements | List, Create, Get, Replace, Delete Entitlement | Entitlement CRUD |
| Entitlement Bundles | List, Create, Get, Replace, Delete Entitlement Bundle | Entitlement bundle CRUD |
| Collections | List, Create, Get, Replace, Delete Collection | Resource collection CRUD |
| Grants | List, Create, Get, Replace Grant | Access grant lifecycle |
| Labels | List, Create, Get, Update, Delete Label | Label CRUD |
| Access Certification Campaigns | List, Create, Get, Delete, Launch Campaign | Access certification campaign lifecycle |
| Dependency | Notes |
|---|---|
Okta Management:latest Integration Model | Import from okta_management-latest.json before importing the project |
Okta Management integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Okta Management — update the adapter_id value in each workflow task if yours is named differently |