---
title: Quick LDAP/AD Definition 
slug: reference-guide-3-0-0/quick-ldapad-definition
description: Learn how to configure an LDAP/Active Directory integration using the Single Connect Setup Wizard with this comprehensive document. Follow step-by-step instructions to add a new LDAP server, define configuration parameters, and explore advanced settings l
docTags: 
createdAt: 2022-08-03T09:57:57.000Z
---

To use the Single Connect Setup Wizard to configure an LDAP/Active Directory integration:

1. Navigate to **Administrator** > **Ldap Manager**.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/k548dKsC38B5-CKYuwryI_image.png" size="80" width="869" height="413" caption="LDAP Manager" position="center" showCaption="true"}

- Click **Add New Ldap Server**. 

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/qvfTQq2HcLupI2RUoxHs0_image.png" size="80" width="607" height="531" caption="LDAP account settings" position="center" showCaption="true"}



1. Enter the related configuration parameters:
   a.	**LDAP Source Name**: a different name must be defined for each LDAP, like ldap1, ldap2, etc.
   b.	**URL**: LDAP IP address and port number
   c.	**Domain**: LDAP domain
   d.	**Username**: read-only user credentials to get the user list information
   e.	**Password**: the username’s password
   f.	**Base DN**: LDAP group area or organization unit
   g.	**Group Search Phase**: The search phase of the imported user groups; must be provided as (objectClass=group).
   h.	**User Search Phase**: The search phase of the imported users; must be provided as (objectClass=user)
   i.	**Principal Key**: Represents user information which sends to AD for authentication. For instance, if we use only the question mark(**?**), the username is only sent to AD for authentication but if we use the domain after the question mark (?domain.com) query sends the username with the domain.
   j.	Follow these steps for each LDAP definition.
2. Click the **Save** button.


**Advanced Settings**:

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/fJTLDnPNSPBA8PJTkSD_i_image.png" size="80" width="709" height="354" caption=" LDAP Account Advanced Settings" position="center" showCaption="true"}


**Is Active Directory**: If the LDAP account is a Windows Active Directory,
it should be set as **YES**.

**NIS Net Group Enable**: This parameter only applies to an Oracle 11g LDAP. The value can be set as **YES** or **NO.** The default value isn**NO**. In an Oracle LDAP, there may be a netrgoup entry defined by **objectClass** with the value **nisNetGroup**. If the value is **TRUE**, it enables import of users with the **netgroup** property.

**User Search With Member Of**: If the users have the MemberOf attribute in the LDAP Server, this parameter can be set** Yes** to import users. By default, the Members attribute in the User Group is used to import users.

**User Phone Number Attribute**: Single Connect can send SMS to users by using the **phoneNumber** property of users. When adding users from AD/LDAP, the attributes to be looked at first should be included in this advanced parameter to fill out the users **phoneNumber** property. Multiple attributes can be defined. Starting from the first defined attribute, the **phoneNumber** user property is filled with the first attribute that is full.

**User Personal No Attribute**: When adding users from AD/LDAP, the attributes to be looked at first should be included in this advanced parameter to fill out the users Personal No property . Multiple attributes can be defined. Starting from the first defined attribute, the **Personal No **(personal\_id in database) user property is filled with the first attribute that is full.

**Additional Attributes**: Additional attributes can be added with a comma (,) separator without space. 
For ex: userPrincipalName,objectClass,ubaThreshold.

Usually, LDAP user attributes are taken from AD and filled accordingly for a user, but the email attribute is an
exception. If the email attribute is needed for an LDAP user with no email value on AD, this attribute can be filled on the **User Properties** screen. If the email attribute is filled on AD, the LDAP sync job overwrites this email property.

The attributes are shown on the **User Properties **window in the following figure.

::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/oxfhA2sbDreuRMvsD3G2g_image.png" size="80" width="709" height="374" caption="LDAP User Properties" position="center" showCaption="true"}