Okta - Remove User Extension
  • 06 Mar 2024
  • 2 Minutes to read
  • Dark
  • PDF

Okta - Remove User Extension

  • Dark
  • PDF

Article summary

Okta - Remove User Extension removes a user extension for each Okta user retrieved from the saved query supplied as a trigger (or users selected in the asset table).

To use this action, you must have Okta users in your Axonius environment.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

General Settings

  • Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
  • Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
  • Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
  • Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
  • Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

  • Use stored credentials from the Okta Adapter - Select this option to use the first connected Okta adapter credentials.

To use this option, you must successfully configure an Okta adapter connection.

Required Fields

These fields must be configured to run the Enforcement Set.

Additional Fields

These fields are optional.

  • Send a deactivation email to the administrator - When selected, an email is sent to the Okta administrator to notify that the user extension was removed.

Connection Parameters

When Use stored credentials from the Okta adapter is toggled Off, these fields are required:

  • Okta URL - The hostname or IP address of the Okta server. This field format is '[instance].okta.com'.
  • Okta API Key - An API key, created in the admin panel. For details, see Creating an API Token in Okta.
  • Number of parallel requests (default: 75) - Specify the maximum parallel requests that will be created when connecting to the value supplied in Okta URL.
  • Throttling rate percentage (default: 10) - Specify the threshold percentage of the Okta API rate limit when connecting to the value supplied in Okta URL. Axonius will stop the data fetch when the API rate limit reaches the supplied value.
    • Gateway Name - Select the gateway through which to connect to perform the action.


Axonius uses the Core Okta API.


The value supplied in Okta API Key must have write or admin permissions.

Required Ports

Axonius must be able to communicate with the value supplied in Connection Settings via the following ports:

  • TCP port 443
  • TCP port 80

Version Matrix

This adapter has only been tested with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

Okta 4.5Yes

For more details about other Enforcement Actions available, see Action Library.

Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.