Contents x
    Okta - Add or Remove Users to/from Group
    • 12 Nov 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Okta - Add or Remove Users to/from Group

    • Updated on 12 Nov 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Okta - Add or Remove Users to/from Group adds or removes users to or from an Okta group for each user returned by the selected query or assets selected on the relevant asset page to an Okta group.

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

    Note:

    Required Fields

    These fields must be configured to run the Enforcement Set.

    • Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
    • 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.

    Note
    To use the actions below, you must have Okta users in your Axonius environment.
    • Use stored credentials from the Okta Adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
      • When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
    Note:

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

    • Group Member Operation - Select the operation to perform either 'Add User To Group' or 'Remove User From Group'
    • Group Name - the name of the group to which the user will be added or removed from.

    • Compute Node - 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.

    • Authentication (default: API Key) - The type of authentication to use.
    • Okta API Key (Access via API Token) - An API key, created in the admin panel. For details, see Creating an API Token in Okta.
    • Okta Client ID (Access via OAuth2) - Client ID of the service app. This is required when OAuth2 is selected in the Authentication drop-down.
    • Okta JWK Private/Public Keys - The JSON web key which was generated and assigned in the OAuth 2.0 service app integration in the Admin Console of Okta. This is required when OAuth2 is selected in the Authentication drop-down.
    • 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.
    • Number of parallel requests (default: 75) - Specify the maximum parallel requests that will be created when connecting to the value supplied in Okta URL.
    • Gateway Name - Select the Gateway through which to connect to perform the action.

    APIs

    Axonius uses the Okta Groups API.

    Permissions

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

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


    Was this article helpful?
    What's Next