← ClaudeAtlas

okta-testslisted

Use when an app uses Okta as its identity provider and needs tests for org config, sign-in policies or Identity Engine flows: per-PR or shared orgs, MFA enforcement, factor enrollment, recovery, SCIM provisioning and least-privilege API tokens.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# okta-tests ## Overview The current Okta platform (Okta Identity Engine, OIE) replaces the older Okta Classic engine; tests target OIE for new orgs. Tests against an Okta org fall into four layers: 1. **Org-level config** - apps, users, groups, sign-in policies; tested via Okta API or Terraform Okta provider for env parity. 2. **Auth flow** - exercise OIDC endpoints from the application. 3. **Sign-in policy + MFA** - verify enforcement of factor requirements per app + per user-group. 4. **OIE workflows** - factor enrollment, recovery flows, SCIM provisioning. ## When to use - The repo uses Okta as IdP (often enterprise or B2B SaaS). - The team has multiple Okta orgs (dev / staging / prod) needing config parity. - Sign-in policies (per-app MFA, IP restrictions, device trust) need integration coverage. - SCIM provisioning hooks need verification. ## Step 1 - Org strategy | Pattern | Pros | Cons | |---|---|---| | Per-PR Okta Developer Edition org (free tier) | Isolated; safe destructive tests | Spin-up time + manual approval to create new orgs | | Shared dev org + namespaced fixtures (`pr-123-*` user prefixes) | Cheap; no spin-up | Cleanup discipline required | | Mocked OIDC server | No Okta dep; fast | Misses Okta-specific behavior | For new flows, prefer **per-PR org**; for app-side flow tests on a stable Okta config, **mocked OIDC** is fine (cross-ref Auth0 Step 7). ## Step 2 - Org config parity Manage org config as code: - **Terraform Okta provider*