Create an integration to manage access for sets of people in your Okta Group membership
Administrators can create groups in Okta to efficiently manage access rights and application settings for distinct sets of users. Users can leverage groups to streamline and secure their access to various applications and resources across multiple devices and environments.
Through this integration, Apono helps you securely manage access for sets of users in your Okta Group instance.
Apono Connector
On-prem connection serving as a bridge between an Okta Group instance and Apono:
Okta Account Access
Okta account with Super Admin privileges to the Okta admin dashboard
This article provides a simplified guide to creating an Okta application for use with Apono.
Since Okta products evolve, we strongly recommend verifying the steps in this documentation with Okta's official App integration documentation.
Follow these steps to create an Okta app:
In your Okta admin dashboard, from the main side navigation, click Applications > Applications > Create App Integration. The Create a new app integration popup window appears.
Select API Services.
Click Next. The New API Services App Integration page appears.
Enter an App integration name, such as Apono Connector.
Click Save. The application settings page appears.
Generate client credentials and a secret for Apono.
Configure the General Settings of the application.
Use the following steps to generate your client credentials:
For the OKTA Groups integration, use an OKTA API Services app that only has one key pair.
On the General tab, under Client Credentials, click Edit.
Copy and save the Client ID.
For the Client authentication, select Public key / Private key. The PUBLIC KEYS section appears.
Under PUBLIC KEYS, click Add key. The Add a public key popup window appears.
Click Generate new key.
Under Private key - Copy this!, click Copy to clipboard and save the value.
Click Done.
Click Save. The Existing client secrets will no longer be used popup window appears.
Click Save.
Create an Apono secret for your Okta instance with your Okta client ID and private key.
Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separate the Apono web app from the environment for maximal security.
You can also input the Okta credentials directly into the Apono UI on the Apono tab in the Secret Store section.
Follow these steps to configure app settings:
On the General tab, under General Settings, click Edit.
For the Proof of possession, uncheck Require Demonstrating Proof of Possession (DPoP) header in token requests.
Click Save.
Follow these steps to define the scope:
On the Okta API Scopes tab, in the okta.groups.manage row, click Grant. The Grant Okta API Scope popup window appears.
This permission allows Apono to manage existing groups in your Okta organization.
Click Grant scope.
In the okta.users.read row, click Grant.
This permission allows Apono to read the existing users' profiles and credentials.
Follow these steps to grant admin assignments:
On the Admin roles tab, click Edit assignments.
From the Role dropdown menu, select Organization Administrator.
To grant users a membership to a group that contains admin roles, the Super Admin role should be granted to the Apono connector.
Click Save Changes.
You can also use the steps below to integrate with Apono using Terraform.
In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.
Follow these steps to complete the integration:
On the Catalog tab, click Okta Group. The Connect Integration page appears.
Under Discovery, click Next. The Apono connector section expands.
From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Integration Name
Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
Okta Organization URL
Organizational URL of the Okta instance to connect
Click Next. The Secret Store section expands.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Custom Access Details
(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
Integration Owner
From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.
NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner
Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.
NOTE: When this setting is defined, an Integration Owner must also be defined.
Click Confirm.
Now that you have completed this integration, you can create access flows that grant permission to your Okta Group instance.
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :
