Identity & security
Okta
Set up the Okta connection, with the setup script or by hand.
Dave connects through an API Services app in your Okta org. First choose what Dave can do:
- Read-only: look things up, never change anything.
- Read and write: also make the changes you approve, such as suspending a user or fixing group membership.
Connect with the setup script
Section titled “Connect with the setup script”The script creates the app with the permissions for your choice. You need an API token from a super administrator; it stays on your machine.
-
In Dave, go to Integrations → Add integration → Okta.
-
Set a Label, e.g.
acme, and your Okta org URL, e.g.https://acme.okta.com. For read and write, tick Enable agentic JIT (advanced). -
Choose Connect Okta, then run the command Dave shows in a terminal with
curlandjq. -
When asked, paste a super administrator API token from Security → API → Tokens.
-
When the script prints Done, return to Dave and revoke the API token.
If the script fails, fix the error it prints and run it again.
Connect manually
Section titled “Connect manually”Skip the steps marked Read and write only for read-only.
-
Read and write only. In Security → Administrators:
- Roles → Create new role: name it
Dave directory actionsand tick the permissions in Dave directory actions role. - Resources → Create new resource set: name it
Dave directoryand add All users and All groups.
- Roles → Create new role: name it
-
Applications → Applications → Create App Integration → API Services → Next. Name it
Dave, choose Use Okta-generated client ID, and save. Copy the Client ID. -
On the General tab, under Client Credentials:
- Edit → Public key / Private key → Add key → Generate new key.
- Switch the key to JSON, copy it (Okta shows it only once), and choose Done.
- Untick Require Demonstrating Proof of Possession (DPoP) header in token requests, then Save.
- Check the key is Active.
-
Okta API Scopes tab: grant the scopes for your choice.
-
Admin roles tab: assign the roles for your choice.
-
In Dave, go to Integrations → Add integration → Okta. Set a label and your Okta org URL, tick I’ll create the Okta app myself, paste the client ID and the private key JSON, and choose Connect Okta.
If it fails, fix the app in Okta and add the integration again with the same label.
Permissions
Section titled “Permissions”Grant only what’s ticked for your choice.
Okta API Scopes tab
Section titled “Okta API Scopes tab”Choose Grant next to each scope.
| Scope | Read-only | Read and write |
|---|---|---|
okta.users.read |
✓ | ✓ |
okta.groups.read |
✓ | ✓ |
okta.apps.read |
✓ | ✓ |
okta.logs.read |
✓ | ✓ |
okta.roles.read |
✓ | ✓ |
Any other .read scope, e.g. okta.devices.read |
Optional | Optional |
okta.users.manage |
✓ | |
okta.groups.manage |
✓ |
Admin roles tab
Section titled “Admin roles tab”Choose Edit assignments, add these, and Save.
| Role | Resource set | Read-only | Read and write |
|---|---|---|---|
| Read-only Administrator | — | ✓ | ✓ |
Dave directory actions |
Dave directory |
✓ |
Dave directory actions role
Section titled “Dave directory actions role”Read and write only. Search for and tick exactly these. Tick each one, not its parent: a parent such as Manage users also grants deleting users.
| Section | Permission |
|---|---|
| User | View users and their details |
| User | Create users |
| User | Activate users |
| User | Deactivate users |
| User | Suspend users |
| User | Unsuspend users |
| User | Unlock users |
| User | Clear users’ sessions |
| User | Reset users’ passwords |
| User | Set users’ temporary password |
| User | Reset users’ authenticators |
| User | Edit users’ profile attributes |
| User | Edit users’ group membership |
| Group | View groups |
| Group | Manage group membership |
Troubleshooting
Section titled “Troubleshooting”| Error | Fix |
|---|---|
| Okta didn’t accept Dave’s key | Check the client ID, and that the key is Active on the General tab. |
| The Okta app is missing required scopes | Grant the scopes the error names on the Okta API Scopes tab. |
| The Okta app requires DPoP | Untick the DPoP requirement on the General tab. |
| The Okta app has no admin role | Assign Read-only Administrator on the Admin roles tab. |
The script fails at assigning … role |
Use an API token created by a super administrator. |