Login
Contents x
Okta - Enable Users
  • 17 Jan 2023
  • 2 Minutes to read
  • Print
  • Dark
    Light
  • PDF
Contents

Okta - Enable Users

  • Updated on 17 Jan 2023
  • 2 Minutes to read
  • Print
  • Dark
    Light
  • PDF

Okta - Enable Users enables each user by reactivating, or unsuspending the users retrieved from the saved query supplied as a trigger (or users selected in the asset table).

Note
To use thiis actions, 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 Axonious. You can change the name according to your needs.
  • Add description (optional) - 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 - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
  • Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.

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

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

Required Fields

These fields must be configured to run the Enforcement Set.

  1. Action to perform on Okta Users - Select the action to perform on the Okta users, either to Unsuspend or Reactivate the users.
  2. Instance Name - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.

Additional Fields

These fields are optional.

  1. Okta URL - The hostname or IP address of the Okta server. This field format is '[instance].okta.com'.

  2. Okta API Key - An API key, created in the admin panel. For details, see Creating an API Token in Okta.

  3. Number of parallel requests (default: 75) - Specify the maximum parallel requests that will be created when connecting to the value supplied in Okta URL.

  4. API rate limit threshold 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.

  5. HTTPS Proxy - A proxy to use when connecting to the value supplied in Okta URL.

Note:

If Use stored credentials from the Okta adapter is not enabled, the fields above are required.

  1. Tunnel Name - For Axonius-hosted (SaaS) deployments. Select the tunnel through which to connect to perform the action.

APIs

Axonius uses the Core Okta API.

Permissions

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.

Version Supported Notes
Okta 4.5 Yes

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

What's Next
Change password!
Changing your password will log you out immediately. Use the new password to log back in.
Change profile
Success!
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.
Logout