Okta

Connect Furl to Okta for user directory and identity management.

Description

Okta integration provides access to identity and access management capabilities, allowing retrieval of user information, group memberships, and organizational structure. Furl leverages this integration to map users to devices, support user targeting in remediations, and enrich context for accountability.

Configuration Steps

1. Generate API Key: Follow the steps below to create an SSWS API key in Okta
2. Get Domain: Note your Okta organization domain (e.g., if your Okta URL is https://acme.okta.com, your domain is acme)
3. Configure in Furl: Enter your API key and domain in the Furl integration settings

Steps to Create an API Key in Okta

1. Sign in to the Okta Admin Console

   1. URL format: https://<your-org>.okta.com/admin
   2. You must have the Super Admin or appropriate administrative role

2. Navigate to the API Token Section

   1. In the left-hand sidebar, go to Security → API
   2. Click the Tokens tab at the top

3. Create a New Token

   1. Click the “Create Token” button
   2. Enter a name for the token (e.g., furl-integration)
   3. Click “Create Token”

   Important: After this step, you’ll be shown the token once only. Copy it and store it securely in a password manager or environment variable. You won’t be able to retrieve it again.

Required Configuration

API Key Connection

• API Key: Your Okta API key retrieved from the Okta admin console
• Domain: Your Okta organization domain (e.g., acme for https://acme.okta.com)

The integration will automatically construct the full URL as https://<domain>.okta.com.

Supported Capabilities

Datasources

• Users → Import user directory information to map users to devices and support user targeting in remediations
  • Primary Source: Can be configured as the primary source of people in your organization

Actions

Currently no actions are supported for this integration.

Troubleshooting

• If Furl returns 401, the SSWS API token is invalid or has been revoked. Generate a new one in the Okta Admin Console.
• Verify the Domain matches your Okta tenant — acme for https://acme.okta.com. Typing the full URL or including https:// will fail.
• If users are missing, check that the API token’s owner has the Super Admin role (or another role with directory read access). Token permissions inherit from the creating user.
• If a previously-working token stops working, check whether the user that created it has been deactivated. Token lifetime is tied to that user.