okta in twins and put this configuration under seed_config.okta.
Okta identity and access management organization with users, groups, application integrations, event hooks, sessions, authentication/MFA, policies/rules, group rules, user types/profile schemas, network zones, custom authorization servers/OIDC/PKCE/consent, organization customization/security, federation/authenticators/devices, directory extensions, admin roles, provisioning and Shared Signals.
Example seed
This is the complete Scenario request body for creating a Scenario. You can also import it witharga test-runner scenarios import --file scenario.json.
Parameters
The following fields belong directly insideseed_config.okta. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.
Seeding behavior
Use explicit resource IDs insidemanagement and exported subsystem maps. Alias resolution does not apply inside those maps. Preserve required built-in user types and schemas when replacing their collections. Password/MFA controls belong in config.
Resource fields
These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.users[]
groups[]
applications[]
applications[].users[]
applications[].groups[]
event_hooks[]
Typed configuration objects
Named object types in the parameter table use these fields.OktaTwinConfig
FailureRule
See Scenario seeding for saving, provisioning, and resetting fixtures.

