Contents x
    Okta - Assign User to Applications
    • 20 Nov 2024
    • 4 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Okta - Assign User to Applications

    • Updated on 20 Nov 2024
    • 4 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    Okta - Assign User to Applications assigns one or more selected SSO applications to:

    • Users returned by the query selected or users selected on the Users page.
    • User assets resolved from Workflows.

    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.

    • Use stored credentials from 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.

    • Application Names - From the dropdown, select one or more applications to assign to each user. Once done, click outside the dropdown. The application names appear in the box. You can remove an application by clicking the X adjacent to its name.

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

    • Okta URL - The hostname or IP address of the Okta server. This field format is '[instance].okta.com'.
    • Authentication - Select whether to authenticate this adapter connection with an API Key (default) or OAuth2 (private/public keys).
    • Okta API Key (Access via API Token) - The generated API key provided by Okta (in the Admin console) that allows Axonius to fetch data from the Okta API. This is required when API Key is selected in the Authentication dropdown (above field). 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 dropdown (above field).
    • Okta JWK Private/Public Keys (Access via OAuth2) - 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 - 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 - Specify the maximum parallel requests that will be created when connecting to the value supplied in Okta URL.
    • Admin URL - The hostname or IP address of the Okta admin server. This field format is '[instance]-admin.okta.com'.
    • Admin Username - The value you enter in the Username field in Okta for the new user you created to allow Axonius to fetch SaaS Management data.
    • Admin Password - The password you set for the new user in Okta.
    • 2FA Secret Key - The secret generated in Okta for setting up 2-factor authentication for the Okta user created for collecting SaaS Management data.
    • SSO Provider - If your organization uses Okta for SSO, you can select this option. For more information, see Connecting your SSO Solution Provider Adapter.
    • Department Field (default: department) - This is the mapping of the department value for the Okta authentication object. Check if your organization's 'department' value is different from the default value ('department').
    • User Filter Params - You can use the Okta Expression language to filter a subset of users (for example, users who belong to specific departments) to be retrieved by the Okta adapter and displayed in Axonius.
    • Filters users by group name - Enter a group name to only fetch users from the specific group. Refer to Configuring a Group in Okta for details.
    • Add users inside the devices - Enable this option to fetch user information to populate in the relevant device-specific fields.
    • HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
    • Justification reason - Enter the reason for assigning the group to the user.
    • Gateway Name - Select the Gateway through which to connect to perform the action.

    APIs

    Axonius uses the following Okta Developer API endpoint:

    Following the run of this action, re-fetch the user's applications using the following endpoint:

    Required Ports

    Axonius must be able to communicate with the following ports:

    • TCP port 443
    • TCP port 80
    • Version M

    Required Permissions

    The stored credentials, or those provided in Connection and Credentials, must have the okta.apps.manage permission to perform this Enforcement Action.

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


    Was this article helpful?
    What's Next