LDAP is one of the most commonly used application protocols for accessing and maintaining corporate user directories. Helix TeamHub can be configured to use corporate LDAP for authentication. Once LDAP authentication is enabled, all successful login attempts either create a new Helix TeamHub user, or update an existing one along with the LDAP group information. The configuration process is explained below:
Configuring LDAP Authentication
To enable LDAP authentication, browse to Helix TeamHub Admin at
http(s)://[hostname]/admin. From the Admin pane, click on the Preferences link in the navigation bar.
Choose the LDAP authentication option and specify the hostname and port of the LDAP server. The hostname might use a URL like
ldap.acme.com or an IP like
10.0.0.30. The port of the LDAP server might vary depending on the connection type. For secure communication between Helix TeamHub and the LDAP server, choose either StartTLS or LDAPS encryption method.
Both as the authentication option to create local Helix TeamHub users while still using LDAP authentication. Note that once
Both is enabled, all Helix TeamHub users will be able to set their local passwords and Helix TeamHub will only attempt to bind to LDAP when built in authentication is unsuccessful.
The Domain search user performs lookups to authenticate other accounts when users sign in. The Domain search user is typically a service account used specifically for third-party integrations. For the Domain search user, only read-access to LDAP is needed.
Use the fully qualified user name, which would look something like this:
The User search base function specifies the fully qualified name of the starting point in the LDAP tree to search for users. If no search filters are specified, then the User search base will retrieve the entire data set.
A user search filter can be used to specify conditions that must be met for a record to be included when searching for users. This setting is optional.
The Account ID field is the name of the LDAP attribute used as the account login. For most Active Directory installations this will be
sAMAccountName. For other LDAP solutions like OpenLDAP, the value of this field is usually
The Account email field is the name of the LDAP attribute used as the account email. Usually the value of this field is
Note: The Account first name and last name fields are optional.
The User LDAP groups field is the name of the LDAP attribute used for finding LDAP groups for a user. Check
User entries contain group information if the directory allows finding LDAP group information directly from user entries. The name of the LDAP field is commonly
Otherwise set the value of the field to either
memberUid depending on the LDAP schema, and set the base path where to search for groups.
Collaborators use built-in authentication by default. LDAP authentication can also be enabled for collaborators by using a different search base or search filter from normal users. Use the
Test LDAP connection feature to search for a user and a collaborator account, and make sure it returns only either a user or a collaborator.
If using Helix TeamHub LDAP Sync application to keep user details up-to-date, enter the unique LDAP source identifier and also add it to the LDAP sync configuration file. Once configured, Helix TeamHub will keep the newly created account details in sync with this LDAP.
Finally, use the
Test LDAP connection feature to test the validity of the configuration. Enter an email or ID of an account and verify that correct results are returned.
To go even further with integrating the Helix TeamHub installation to the corporate LDAP, consider keeping user accounts in sync with Helix TeamHub LDAP Sync application.
When changing the authentication method back from LDAP to built-in, all users that have been created via LDAP will need to perform a password reset to login again. After the authentication method changes, users will not be able to edit any user attributes that were originally synced from LDAP (e.g. username, email and password).