Help Center

SpinOne Integration with Okta Directory

SpinOne’s Okta Directory integration lets SpinOne read users, groups and devices from your Okta tenant. Once connected, you can see each endpoint’s Okta user and their groups in SpinOne, and use Okta groups in allowlists, blocklists and security policies.

The integration uses an Okta API Services app with read-only access. SpinOne never creates, updates or deletes anything in Okta.

Note: This is separate from the SpinOne Okta SSO integration, which lets your team sign in to SpinOne with Okta. The two are set up separately.

Before you start

  • Your Okta domain, for example yourcompany.okta.com.
  • An Okta Super Admin account, needed to create app integrations and grant API scopes.
  • Access to the SpinOne console as an administrator.

How to connect your Okta directory

Step 1: Create an API Services app in Okta

In the Okta Admin Console, go to Applications > Applications and click Create App Integration.

Select API Services as the sign-in method and click Next. (If the dialog shows tabs, switch to Classic experience first.)

Enter a name for the app (for example, SpinOne Directory Sync) and click Save.

On the app’s General tab, copy the Client ID from the Client Credentials section. You will need it in Step 3.

Step 2: Enable DPoP

On the app’s General tab, in the General Settings section, click Edit.

Under Proof of possession, enable Require Demonstrating Proof of Possession (DPoP) header in token requests.

Click Save.

Step 3: Create the connection in SpinOne and download the public key

In the SpinOne console, go to Integrations > External Integrations, find Okta and click View connections.

Click Add connection and select Directory Sync.

Enter a Title, your Domain and the Client ID from Step 1, then click Create.

Domain field: enter only the first part of your domain and choose the ending (.okta.com, .oktapreview.com, …) from the dropdown. Don’t paste the full domain.

In the new connection’s menu (⋮), select Download public JWK. A small JSON file is saved to your computer.

Step 4: Add the public key in Okta

Return to the Okta app’s General tab and scroll to the Public keys section.

Click Edit. Keep Configuration set to Save keys in Okta, then click Add.

Paste the contents of the JWK file downloaded in Step 3 and click Save.

Click Save for the Public keys section. The key appears with Status: Active and Key use: sig.

Tip: if the file opens in your browser’s JSON viewer, use Raw Data > Copy so you copy the actual JSON, not the formatted view.

Step 5: Switch client authentication to Public key / Private key

In the Client Credentials section, click Edit.

Under Client authentication, select Public key / Private key.

Click Save.

Note: Okta saves this option only after an active public key exists (Step 4). Okta requires this method for service apps that use Okta API scopes.

Step 6: Grant Okta API scopes

Open the Okta API Scopes tab.

Click Grant for each of these scopes: okta.users.read, okta.groups.read, okta.devices.read.

All three scopes are read-only.

Step 7: Assign an admin role

Open the Admin roles tab and click Edit assignments.

Assign the Read-only Administrator role and save.

Important: the role is required in addition to the scopes. Okta grants access only where the role and the scopes overlap; without the role, SpinOne’s requests are rejected (HTTP 403).

Step 8: Test the connection in SpinOne

Return to Integrations > External Integrations > Okta. The connection should show Status: ACTIVE.

Click Test Connection. You should see Connection Successful.

SpinOne imports your Okta users, groups and devices during the next account import: when you click Update user list, or automatically once a day.

What happens after you connect

  • The Endpoints page shows each device’s Okta user and Okta groups, with Okta filters and tabs.
  • On All Apps > Allowlist and Blocklist, the Okta Groups tab becomes available.
  • In Security Policies, you can use List of Okta groups as a scope or exception.
Was this helpful?