Connect Okta

Before you start

You need the Okta super administrator admin rights described below, and in Trusterio the right to manage integrations (owners and admins have it). Anybody else sees the page read-only.

Connect it

1. Open Automation and choose Connect on the Okta super administrator card. (The link opens the dialog straight away.)
2. Give it a name under What to call it, and read What to grant: every permission and what it is for.
3. Press Add it and enter the credential. You land on the connection’s own page.

In Okta

1. Okta tokens cannot be limited, and a token has the rights of whoever made it. So first create an integration user with the Read-only Administrator role.
2. Sign in as that user and create a token under Security → API → Tokens.

In Trusterio

Fill in your Okta org URL (EU tenants are on okta-emea.com), the Data region and the API token, and press Save credentials.

What it reads

Users, active and deprovisioned; sign-on and password policies and their rules; who holds an admin role, directly or through a group.

What it checks

• MFA required by policy, password policy strength, session lifetime bounded
• Inactive accounts, and deprovisioned accounts cleared

After it is connected

• Press Sync now for the first reading. The Tests tab shows each check: what it should be, what was found, and what is affected.
• New connections are read by hand until you choose a schedule: in Monitoring, on the Collection tab, pick Every hour, Every 6 hours, Daily or Weekly.
• The page says when it was last read and its health; Sync History keeps every run.

A connection marked Beta on the Automation screen has not been tried on a real account yet: its permission list is our reading of the provider’s documentation. AWS, Azure, Google Cloud and Jira have been. If a permission is wrong, tell us.

Disconnect

On the connection’s page, choose Disconnect. Reading stops and its credentials are deleted; its history, checks and evidence stay. Then remove what you created at the provider:

• Revoke the token, and deactivate the integration user.