--- title: "Okta: Configuring the Remediation Actions Integration" slug: "okta-configuring-the-remediation-actions-integration" updated: 2026-11-15T13:57:08Z published: 2026-11-15T13:57:08Z canonical: "knowledge.catonetworks.com/okta-configuring-the-remediation-actions-integration" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.catonetworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Okta: Configuring the Remediation Actions Integration ## Overview XOps integrations let you take response actions in connected third-party applications as part of an investigation. You can revoke a user’s sessions or disable their account in your single sign-on (SSO) provider or a specific application. These actions help you contain threats by restricting access to affected accounts. To enable these actions, configure a connector for the relevant third-party application. For more information, see [Mitigating Threats in XOps Stories](/v1/docs/mitigating-threats-in-xops-stories). To configure the Remediation Actions integration, you need to: 1. Configure the required settings in the SaaS application 2. Create the API connector in the CMA A XOps license is required for Remediation Actions integrations. ### Benefits of Connecting Okta The Okta Remediation Actions connector lets Cato take response actions on Okta user accounts during an investigation. It uses a separate API token, without affecting other Okta connectors, such as App Activities. - **Disable User:** Finds the user whose Okta login or primary email matches the requested email and deactivates the account. The account status becomes **Deprovisioned**. If the account is already deactivated, the action reports that condition and succeeds. - **Revoke Sign-In Sessions:** Finds the user whose Okta login or primary email matches the requested email and clears all active Okta sessions. It revokes the OpenID Connect and OAuth access and refresh tokens issued to the user. It also clears remembered multifactor authentication (MFA) devices, prompting the user for MFA on the next sign-in on every device. The account is not deactivated. The action works for any user status, including deactivated users. Each action runs on one user, identified by email, and reports **Completed** or **Failed** with a reason. ## Configuring the Okta Integration To configure the integration, identify your Okta domain, create a dedicated API token, and create the connector in the Cato Management Application (CMA). ### Prerequisites - An Okta administrator account that can create API tokens, deactivate users, and clear their sessions. Use the **Super Administrator** role or a custom administrator role with these permissions: Both lifecycle permissions are also included in `okta.users.lifecycle.manage`. - `okta.users.read` - `okta.users.lifecycle.deactivate` for **Disable User** - `okta.users.lifecycle.clearSessions` for **Revoke Sign-In Sessions**, displayed as **Clear users' sessions** in the Admin Console An API token inherits the permissions of its creating account. The **Read-Only Administrator** role used for App Activities is insufficient. Use a dedicated account whose lifecycle and permissions are managed for this integration. Deactivating the account also deactivates its API tokens. ### Step 1: Configure the Integration in Okta Use your Okta organization's base URL, including `https://`, as the **Okta Domain URL**. Examples include: - `https://companyname.okta.com` - `https://companyname.okta-emea.com` - `https://companyname.oktapreview.com` Do not use an Admin Console URL containing `-admin` or append `/admin`. If your organization uses a custom domain for Okta APIs, use that base URL. For details, see [Okta organizations](https://developer.okta.com/docs/concepts/okta-organizations/). Create a separate SSWS API token for this connector instead of reusing an App Activities token. Treat the token like a password. Do not place it in source control, tickets, or chat. **To configure the integration in Okta:** 1. Identify the base URL for your Okta organization. Copy and save the **Okta Domain URL** so it can be entered into the CMA. 2. Sign in to the Okta Admin Console with the dedicated account. 3. Navigate to **Security > API**. 4. Select the **Tokens** tab. 5. Click **Create token**. 6. Enter a descriptive name, such as `Cato Remediation Actions`. 7. Configure the token's network-zone restriction according to your organization's security policy. Ensure the restriction allows the Cato service to connect to your Okta organization. 8. Click **Create token**. 9. Copy and save the **API Token** so it can be entered into the CMA. For the Okta procedure, see [Manage Okta API tokens](https://help.okta.com/en-us/content/topics/security/api.htm). SSWS tokens remain valid for 30 days from creation or last use. Each successful API request refreshes the 30-day inactivity period. Token rotation is manual. **To rotate the API token:** 1. Create a replacement token using the procedure above. 2. Update the connector in the CMA with the replacement token. 3. Confirm that its connection status is **Connected**. 4. Revoke the old token in Okta. ### Step 2: Create the API Connector in the CMA After you have set up an integration with the required application, add the details in the CMA. **To create the API connector in the CMA:** 1. From the navigation menu, click **Resources > Integrations.** 2. Click the **Configured Integrations** tab. 3. Click **New**. The **New Integration** panel opens. 4. Select the **SaaS Application** you want to add. 5. In the **Capability** drop-down, select **Remediation Actions**. 6. Add the details created during step one. - **SaaS Application:** Okta - **Name:** Enter a name for the integration - **Description:** Optionally, enter a description - **Okta Domain URL:** Enter the base URL identified in Step 1 - **API Token:** Paste the token value only, without the `SSWS` prefix 7. Click **Save**. The app is visible on the **Integrated Apps** table with a **Connected** status. ## Known Limitations - **Deactivation is destructive:** Okta deprovisions the user from all assigned apps. This can destroy user data, such as email or files. Okta documents this action as not recoverable. - **Session revocation:** Okta documents that **Revoke Sign-In Sessions** does not clear sessions created for web or native apps. - **Exact email match:** The requested email must match the stored Okta login or primary email exactly, including letter case. Otherwise, the action reports **Failed** with the reason **No Okta user matches the requested email**. - **Token owner:** **Disable User** and **Revoke Sign-In Sessions** cannot target the account that owns the connector's API token. Deactivating that account invalidates the token. - **Connection status:** **Connected** confirms only that the token can list users. Missing deactivation or session-clearing permissions are reported as a **Failed** result when an action runs. - **Token lifecycle:** An SSWS token becomes invalid if its creating account is deactivated. It expires after 30 days without use.