OktaConfig
Okta Configuration Discovery Module for M&A Discovery Suite (config-depth).
What it does
Captures deep Okta configuration for pre-configuring destination systems from CSVs alone. Discovers apps + SAML/OIDC settings, groups + rules, policies (signon/password/MFA) + rules, authorization servers + claims/scopes, identity providers, network zones, hooks. One CSV per object family using static filenames with 'Okta' prefix. Writes OktaConfigManifest.json (schemaVersion, capturedAt, laneUsed, counts). Mirrors VeeamDiscovery.psm1 / IISConfigDiscovery.psm1 / PaloAltoDiscovery.psm1 patterns: - Per-family try/catch (missing feature = debug log + continue) - Honest-empty when unconfigured (laneUsed='none', NEVER fabricate) - @($x).Count everywhere - ASCII-only content written UTF-8 WITH BOM - PowerShell 5.1 only (no -AsUTC, no ternary; hashtable sorting via script-block Sort-Object when ordering) - Pure testable functions: Build-OktaRestQuery, Convert-OktaResponseToRecord - Multi-strategy collection with graceful fallback
How the app exposes it
The module runs through the ACQI discovery orchestrator and writes its rows into a dedicated results view. From there, conflicts, dependencies, and readiness scores feed the deal-wide consolidation layer.
/discovered/okta-config Outputs
Each module emits a normalised CSV keyed by entity ID with readiness and risk scores, evidence-source counts, and last-seen timestamps. The exact column set varies by module — the app's results view shows the live schema.