TrueNAS has an Open LDAP client for accessing the information on an LDAP server. An LDAP server provides directory services for finding network resources like users and their associated permissions.

You can have either Active Directory or LDAP configured on TrueNAS but not both.

To configure TrueNAS to use an LDAP directory server:

Support for LDAP Samba Schema is deprecated in TrueNAS 22.02 (Angelfish) and removed in 24.10 (Electric Eel). Migrate legacy Samba domains to Active Directory before upgrading to 24.10 or later.

The LDAP widget displays after you configure TrueNAS settings for your LDAP instance. The widget includes Status, and the Hostname and Base DN and Bind DN you configured.

TrueNAS provides the option to configure a FreeIPA directory service client using the LDAP configuration screen under Credentials > Directory Services.

You can have either Active Directory or LDAP configured on TrueNAS, but not both.

You must do the following things listed in this section. See the procedure below for detailed steps.

Idmap in Linux is essentially a translation of a range of IDs into another or the same range of IDs.

Only administrators experienced with configuring Id mapping should attempt to add new or edit existing idmaps. Misconfiguration can impact system operation.

The Idmap widget in the Advanced Settings on the Directory Services screen displays idmaps added to TrueNAS.

Organizations can use Microsoft Entra Domain Services (formerly Azure Active Directory Domain Services) to manage users and groups by connecting TrueNAS to an Azure domain and joining the managed directory.

Recommended best practice for increased security and flexible administration is to synchronize Entra ID with an on-premises active directory domain. However, some organizations prefer to use cloud-only domain services. This tutorial outlines how to join TrueNAS to an Entra ID without an on-premises domain.