---
title: Session User (LDAP/AD User) Connection
slug: singleconnect-reference-guide-3-1-0/session-user-ldapad-user-connection
description: Learn how to integrate Single Connect with LDAP/AD to enable users to access target systems using their LDAP/AD credentials. Also, discover how Single Connect seamlessly logs in as an LDAP user when credentials are not configured for the device group. Thi
docTags: 
createdAt: 2022-07-27T12:24:30.000Z
---

If both the target systems and Single Connect are integrated with LDAP/AD, users can log in to target systems with their LDAP/AD credentials. This feature can also be used when the username and password of a Single Connect user is configured as an account with the same username and password in the target system. This user is called a Session User.




If there are no credentials configured for the device group (such as** Manual Login**,** Global User**, **SAPM**, **Secret Data Vault**, or** Assigned Credentials**), Single Connect logs in to the target device as an LDAP user. If any of the credential methods mentioned above are configured, Single Connect will establish the connection with the configured method.


Single Connect allows the selection of the authenticated user that will be able to connect to the target devices. This is explained in the following section. Even if any of the methods mentioned above is configured for the connection, a Session User can be added as a choice. Please refer to section the [Multiple User Selection in RDP Proxy](docId\:wIMpW07U247TYkP8tQQv5) or configuration details.


Some remote devices require FQDN addresses, in addition to a username. In this case, the **useEmailAsUsername** property key should be set as** true **in the device group properties, in order to use both properties to log in to target devices.


If the target device requires FQDN addresses, the following  configuration is required, in addition to the session user property:

1. Navigate to **Device Management **> **Device Groups**.
2. Right-click the device group and select the **Show Properties** option.
3. Set the **useEmailAsUsername** property as** true**.

![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/w5yHAv_5bf3EoW2M_AfkO_image.png "Device Group Properties Configuration to Use Domain User Credentials to Log In")