LDAP Groups

Create an integration to manage users through an LDAP Group

LDAP Groups are fundamental Lightweight Directory Access Protocol (LDAP) components. They enable centralized management of user permissions and access to network resources in complex IT environments.

Through this integration, Apono helps you securely manage the access of your users.

---

Prerequisites

Item	Description
Admin User	Admin user on the LDAP server created for the Apono connector
Apono Connector	On-prem connection serving as a bridge between an LDAP server and Apono: AWS Azure GCP Kubernetes The connector must have Admin permissions to LDAP in order to manage JIT access to LDAP groups.
Apono Secret	Value generated with the credentials of the user you create Create your secret based on the LDAP user credentials and connector you are using. 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.
LDAP Information	Information for the LDAP server: Domain LDAP Server URL Self-signed server or CA certificate* Needed when the server does not have a properly signed certificate with a public CA Groups Scope* Limits Apono to work with groups within the defined scope User Scope* Limits Apono to work with users within the defined scope User Email Attribute* Defines which user email to use * This information is only necessary when the note is applicable.

---

Integrate an LDAP Group

LDAP Group tile

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:

1. On the Catalog tab, click LDAP 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.

If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).

1. Click Next. The Integration Config section expands.

2. Define the Integration Config settings.

   Setting	Description
   Integration Name	Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
   LDAP Server URL	URL for the LDAP server The following are the default LDAP ports to append to the server URL: 389: No SSL 636: SSL
   Self signed server or CA certificate	(Optional) Self-signed certificates or base64-encoded certificate of the self-signed LDAP server or CA certificate Leave this field blank unless the LDAP server does NOT have a properly-signed certificate with a public CA.
   Domain	Domain of the LDAP Server Example: dc=example, dc=com
   Groups Scope	(Optional) Scope of the groups When a scope is entered, Apono will only fetch groups within the specified scope. If this field is blank, Apono will fetch all groups within the LDAP directory.
   Users Scope	(Optional) Scope of the users When a scope is entered, Apono will only fetch users within the specified scope. If this field is blank, Apono will fetch all users within the LDAP directory.
   User Email Attribute	(Optional) Attribute of user emails When an attribute is defined, it enables Apono to determine which email to use. A user email attribute is helpful when users have multiple email addresses. If a user has multiple email addresses, each email address must exist within both the LDAP directory and Apono.

3. Click Next. The Secret Store section expands.

4. Associate the secret or credentials.

5. Click Next. The Get more with Apono section expands.

6. Define the Get more with Apono settings.

   Setting	Description
   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	(Optional) Fallback approver if no resource owner is found Follow these steps to define one or several integration owners: 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	(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several resource owners: 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.

7. Click Confirm.

💡Are you integrating with Apono using Terraform?

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 for more details about the schema definition.

Now that you have completed this integration, you can create access flows that grant access to members of your LDAP Group.