Connect action in the Okta package

Use the Connect action in the Okta package to establish a secure session with Okta by validating the tenant domain and OAuth 2.0 connection.

Prerequisite

Before using the Connect action, you must first configure the Okta app, grant the required scope and set up an OAuth connection in the Control Room by completing the following prerequisite:

Configure the Okta app and grant the required scope
  1. Login to the Okta app as an admin.
  2. Navigate to Applications > Applications on the left menu.
  3. Click Create App Integration.
  4. Select OIDC - OpenID Connect.
  5. Select Web Application and click Next.
  6. Update the App integration name if required.
  7. Under Assignments section, select the right assignment for controlled access, and click Save.
  8. Open the created app integration.
  9. Under General tab, copy the Client ID and Client secret. These details are required while configuring OAuth connection in the Control Room.
  10. Scroll down to find General Settings and click Edit.
  11. Under LOGIN section, for Sign-in redirect URIs, click Add URI and enter the Control Room URI.
  12. Navigate to Okta API Scopes tab and grant these scopes:
    • okta.users.read
    • okta.users.manage
    • okta.groups.read
    • okta.groups.manage

Configure OAuth connection

Connect action uses OAuth 2.0 authentication to safely authenticate and authorize the bot, enabling secure interaction with Okta. Before using the Connect action, ensure the OAuth 2.0 connection is properly configured in the Control Room with the following scopes:
  • okta.users.read
  • okta.users.manage
  • okta.groups.read
  • okta.groups.manage
For more information, see Configure OAuth 2.0 connection in Control Room

Settings

  • Domain URL: Enter the Okta tenant domain to connect to, for example companyabc.okta.com. This field must match the Okta domain.
  • OAuth2 Connection: Enter the Control Room managed OAuth2 connection used for authentication.
  • Okta session: Use one of the following tabs for creating a session:
    • Local session: To specify a session name that can be used only in the current automation.
    • Global session: To specify a session name that can be used across multiple automation, such as parent and child.
      Note: The parent and child bots should have the same package version.
    • Variable: To specify or create a session variable that stores the value.