Skip to main content
DSALTA connects to Okta using read-only API access to collect compliance evidence automatically. Data feeds into your Access accounts page.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Okta environment.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

​
What DSALTA reads

DSALTA reads the Okta user roster — names, emails, account status and creation dates, which appears on your Access page. DSALTA does not read Okta admin-role assignments, so every person is listed with the role User.It calls these Okta endpoints:
  • /api/v1/users
  • /api/v1/users/{id}/factors
  • /api/v1/policies
Permissions the checks require: okta.apps.read, okta.groups.read, okta.policies.read, okta.users.readEvery request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Okta environment.

​
Troubleshooting

There is no Reconnect button. Open Integrations → Connected, click Manage on the Okta card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Okta. This usually happens when API tokens expire.
Verify the connected account still holds the permissions this integration requires. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.