Deploy Auth Code Flow for Okta Directory

1. If you have not already done so, activate the Cloud Identity Engine and obtain the Sign-in redirect URI for Okta.

   1. After activating the Cloud Identity Engine, log in to the hub and select the Cloud Identity Engine app.
   2. Copy the URL for your Cloud Identity Engine tenant and edit it to obtain the Sign-in redirect URI that Okta requires. To edit the URL, replace the text after the domain with /authorize. For example, if your Cloud Identity Engine tenant URL is https://directory-sync.us.paloaltonetworks.com/directory?instance=<InstanceId>, your Redirect URL is https://directory-sync.us.paloaltonetworks.com/authorize.
2. Using the Okta Administrator Dashboard, prepare to add your Okta Directory in the Cloud Identity Engine.

   To set up an Okta Directory in the Cloud Identity Engine, you must create a user then assign Admin Roles to that user to grant privileges for the Okta Directory in the Okta Administrator Dashboard (SecurityAdministratorsAdminsAdd Administrator). This is the account you’ll assign to the app in step 2.6. This is also the same account you'll use to log in for step 8 when using the Auth Code Flow for your Okta Directory.

   1. Create an app integration for the Cloud Identity Engine app in Okta.
   2. Select OIDC - OpenID Connect as the Sign-in method.
   3. Select Web Application as the Application type then click Next.

   4. Replace any existing Sign-in redirect URIs with the edited URL from step 1.2.

      Palo Alto Networks recommends separating regions by aligning region-specific tenants with region-specific Okta accounts. However, for testing, if you have Cloud Identity Engine tenants in more than one region, add Sign-in redirect URIs for each region where you have a tenant.
   5. Skip the steps for Sign-out redirect URIs and Base URIs as these aren't required.
   6. Assign the app to a user or group and Save the configuration.

      Be sure to assign the app only to the administrator you created in the first step.
3. Configure the Okta app integration.

   1. Edit the app you just created then select Refresh Token.

      Using the refresh token is mandatory.

   2. Select Rotate token after every use and increase the Grace period for token rotation to 60 seconds.

   3. Save your changes.
4. Obtain the information about your Okta app integration that you need to configure in the Cloud Identity Engine.

   1. Select General, then copy your Client ID and Secret.

   2. Select your username in the upper right to copy your Okta domain.

5. Assign the app and grant the required permissions for the Cloud Identity Engine to access your Okta directory information.

   1. Select Assignments, then assign the Cloud Identity Engine app to the administrator who configures the Okta integration in the Cloud Identity Engine.

   2. Select Okta API Scopes and grant consent to the following scopes:

      • okta.authorizationServers.read (Required only if you have more than one Okta authorization server)
      • okta.groups.read
      • okta.logs.read
        The Cloud Identity Engine requires this scope to read the following log events only:

        • user.lifecycle.delete.initiated
        • group.lifecycle.delete
        • user.lifecycle.activate
        • user.lifecycle.deactivate

        The Cloud Identity Engine uses a filter to retrieve only these events, it does not receive any other events for this scope.
      • okta.users.read
      • okta.users.read.self

      If you want the Cloud Identity Engine to collect enterprise application data so that it is included when you View Directory Data, you must grant consent to the okta.apps.read scope before you select the option in step 9.

6. In the Cloud Identity Engine app, select DirectoriesAdd Directory.
7. Set Up a Cloud Directory and select Okta.

8. Select the method you want to use to log in to the Okta directory.

   • Auth Code Flow—(Default) To make changes to your Okta directory in the Cloud Identity Engine, you must log in to the Okta directory.
   • Client Credential Flow—By granting the required permissions in advance, you do not need to log in to the Okta directory to make changes to that directory in the Cloud Identity Engine. This option requires additional configuration; for more information, refer to Deploy Client Credential Flow for Okta.
9. Select whether you want to Collect enterprise applications data so that it displays when you View Directory Data.

   For beta users of this feature, the Cloud Identity Engine continues collecting enterprise application data for any directories configured in your tenant during the beta and no further configuration is required. If you configure a new directory, you must select whether you want to collect enterprise application data from the new directory and grant consent for the scope in step 5.2.
10. Specify your Okta Directory information to allow the Cloud Identity Engine to connect to your Okta Directory.

    1. Paste your Okta Directory Domain that you copied in step 4.2.
    2. Paste your Okta Directory Client ID and Client Secret that you copied in step 4.1.

       The Client ID must begin with 0.
11. Click to Sign in with Okta and enter your Okta Directory credentials.

    When the login is successful, Logged In displays. Palo Alto Networks recommends using the built-in authorization server. If you have more than one Okta authorization server, repeat the previous steps for each additional Okta Directory you want to add.

12. Click Test Connection to verify your configuration.

    When the test is successful, Success displays.
13. (Optional) Customize the name the Cloud Identity Engine displays for your Okta Directory.

    By default, the Cloud Identity Engine uses the default domain name.

    You can use up to 15 lowercase alphanumeric characters (including hyphens, periods, and underscores) for the directory name in the Cloud Identity Engine. You don't need to change the name of the directory itself, only the name of the directory in the Cloud Identity Engine app.
14. Submit the configuration.

    You can now use information from your Okta Directory in the Cloud Identity Engine when you configure a user- or group-based Security policy rule or with other Palo Alto Networks applications.

    For optimal performance, the Cloud Identity Engine does not support the default Okta group "Everyone" because Okta does not recommend using this group to define policy rules.