# Okta Groups

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.

***

### Prerequisites

<table><thead><tr><th width="239">Item</th><th>Description</th></tr></thead><tbody><tr><td><strong>Apono Connector</strong></td><td><p>On-prem connection serving as a bridge between an Okta Group instance and Apono:</p><ul><li><a href="/pages/U4HFH35XWDo3jyqhJqgQ">AWS</a></li><li><a href="/pages/ztAsRPKJcMNxeQKE2GNB">Azure</a></li><li><a href="/pages/xPrzAcLGsoliEpPJuozp">GCP</a></li><li><a href="/pages/p5PzUV4THznqePSTYgEH">Kubernetes</a></li></ul></td></tr><tr><td><strong>Okta Account Access</strong></td><td>Okta account with Super Admin privileges to the Okta admin dashboard</td></tr></tbody></table>

***

### Create an Okta application

{% hint style="warning" %}
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](https://help.okta.com/oie/en-us/content/topics/apps/apps_apps.htm).
{% endhint %}

Follow these steps to create an Okta app:

1. 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.
2. Select **API Services**.
3. Click **Next**. The **New API Services App Integration** page appears.
4. Enter an **App integration name**, such as *Apono Connector*.
5. Click **Save**. The application settings page appears.
6. [Generate client credentials](#generate-client-credentials) and a secret for Apono.
7. [Configure the General Settings](#configure-the-general-settings) of the application.
8. [Define the scope](#define-the-scope).
9. [Grant admin assignments](#grant-admin-assignments).

#### Generate client credentials

<figure><img src="/files/hipAxj0GRIlKOfiAJfXe" alt="" width="563"><figcaption><p>Client Credentials section</p></figcaption></figure>

Use the following steps to generate your client credentials:

{% hint style="warning" %}
For the OKTA Groups integration, use an OKTA API Services app that **only has one key pair**.
{% endhint %}

1. On the **General** tab, under **Client Credentials**, click **Edit**.
2. Copy and save the **Client ID**.
3. For the **Client authentication**, select **Public key / Private key**. The **PUBLIC KEYS** section appears.
4. Under **PUBLIC KEYS**, click **Add key**. The **Add a public key** popup window appears.
5. Click **Generate new key**.
6. Under **Private key - Copy this!**, click **Copy to clipboard** and save the value.
7. Click **Done**.
8. Click **Save**. The **Existing client secrets will no longer be used** popup window appears.
9. Click **Save**.
10. [Create an Apono secret](/docs/connectors-and-secrets/apono-integration-secret.md) for your Okta instance with your Okta client ID and private key.

    ```
    "client_id": "<OKTA_CLIENT_ID>"
    "private_key": "<OKTA_JSON_PRIVATE_KEY>"
    ```

{% hint style="info" %}
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](/docs/about-apono/security-and-architecture.md).

You can also input the [Okta credentials](#integrate-okta-group) directly into the Apono UI on the **Apono** tab in the **Secret Store** section.
{% endhint %}

#### Configure the General Settings

<figure><img src="/files/4g4RDkPB0USaoGp22x7Y" alt="" width="563"><figcaption><p>General Settings section</p></figcaption></figure>

Follow these steps to configure app settings:

1. On the **General** tab, under **General Settings**, click **Edit**.
2. For the **Proof of possession**, uncheck **Require Demonstrating Proof of Possession (DPoP) header in token requests**.
3. Click **Save**.

#### Define the scope

<figure><img src="/files/3lCkE9bfV5XO9vcOVJ8t" alt="" width="563"><figcaption><p>Okta APi Scopes tab</p></figcaption></figure>

Follow these steps to define the scope:

1. On the **Okta API Scopes** tab, in the **okta.groups.manage** row, click **Grant**. The **Grant Okta API Scope** popup window appears.

{% hint style="info" %}
This permission allows Apono to manage existing groups in your Okta organization.
{% endhint %}

2. Click **Grant scope**.
3. In the **okta.users.read** row, click **Grant**.

{% hint style="info" %}
This permission allows Apono to read the existing users' profiles and credentials.
{% endhint %}

#### Grant admin assignments

<figure><img src="/files/zBFC9WXGwbfgiMN3TTrV" alt="" width="563"><figcaption><p>Admin roles tab</p></figcaption></figure>

Follow these steps to grant admin assignments:

1. On the **Admin roles** tab, click **Edit assignments**.
2. From the **Role** dropdown menu, select **Organization Administrator**.

{% hint style="info" %}
To grant users a membership to a group that contains admin roles, the **Super Admin** role should be granted to the Apono connector.
{% endhint %}

3. Click **Save Changes**.

***

### Integrate Okta Group

<figure><img src="/files/6w570uxzuNc7SZsO5o91" alt="" width="563"><figcaption><p>Okta Group tile</p></figcaption></figure>

{% hint style="success" %}
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.
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=okta+group) tab, click **Okta Group**. The **Connect Integration** page appears.
2. Under **Discovery**, click **Next**. The **Apono connector** section expands.
3. 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.

{% hint style="success" %}
If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](/docs/aws-environment/apono-connector-for-aws.md), [Azure](/docs/azure-environment/apono-connector-for-azure.md), [GCP](/docs/gcp-environment/apono-connector-for-gcp.md), [Kubernetes](/docs/kubernetes-environment/apono-connector-for-kubernetes.md)).
{% endhint %}

4. Click **Next**. The **Integration Config** section expands.
5. Define the **Integration Config** settings.

   <table><thead><tr><th width="210">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration Name</strong></td><td>Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow</td></tr><tr><td><strong>Okta Organization URL</strong></td><td>Organizational URL of the Okta instance to connect<br>For example: <code>https://mycompany.okta.com</code></td></tr></tbody></table>
6. Click **Next**. The **Secret Store** section expands.
7. [Associate the secret or credentials](/docs/connectors-and-secrets/apono-integration-secret.md).
8. Click **Next**. The **Get more with Apono** section expands.
9. Define the **Get more with Apono** settings.

   <table><thead><tr><th width="209">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Credential Rotation</strong></td><td>(Optional) Number of days after which the database credentials must be rotated<br><br>Learn more about the <a href="/pages/UsMtClaCM1SlvPsARUsM">Credentials Rotation Policy</a>.</td></tr><tr><td><strong>User cleanup after access is revoked (in days)</strong></td><td><p>(Optional) Defines the number of days after access has been revoked that the user should be deleted</p><p><br>Learn more about <a href="/pages/zJwQEG15iEhbPYg9hpqp">Periodic User Cleanup &#x26; Deletion</a>.</p></td></tr><tr><td><strong>Custom Access Details</strong></td><td>(Optional) Instructions explaining how to access this integration's resources<br><br>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 <strong>400 characters</strong>.<br><br>To view the message as it appears to end users, click <strong>Preview</strong>.</td></tr><tr><td><strong>Integration Owner</strong></td><td><p>(Optional) Fallback approver if no <a href="/pages/Ey4wuziyr2BzKYQnd5am">resource owner</a> is found<br><br>Follow these steps to define one or several integration owners:</p><ol><li>From the <strong>Attribute</strong> dropdown menu, select <strong>User</strong> or <strong>Group</strong> under the relevant identity provider (IdP) platform.</li><li>From the <strong>Value</strong> dropdown menu, select one or multiple users or groups.</li></ol><p><br><strong>NOTE</strong>: When <strong>Resource Owner</strong> is defined, an <strong>Integration Owner</strong> must be defined.</p></td></tr><tr><td><strong>Resource Owner</strong></td><td><p>(Optional) Group or role responsible for managing access approvals or rejections for the resource<br><br>Follow these steps to define one or several <a href="/pages/Ey4wuziyr2BzKYQnd5am">resource owners</a>:</p><ol><li>Enter a <strong>Key name</strong>. This value is the name of the tag created in your cloud environment.</li><li>From the <strong>Attribute</strong> dropdown menu, select an attribute under the IdP platform to which the key name is associated.<br><br>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.</li></ol><p><br><strong>NOTE</strong>: When this setting is defined, an <strong>Integration Owner</strong> must also be defined.</p></td></tr></tbody></table>
10. Click **Confirm**.

<details>

<summary>💡Are you integrating with Apono using Terraform?</summary>

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**:

1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code.
2. Click to copy the code.
3. Make any additional edits.
4. Deploy the code in your Terraform.

Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/okta-group) for more details about the schema definition.

</details>

Now that you have completed this integration, you can create [access flows](/docs/access-flows/access-flows.md) that grant permission to your Okta Group instance.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apono.io/docs/additional-integrations/identity-providers/okta-groups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.