LDAP Auth Module
An LDAP authentication module lets users log in to Hub and any connected services with credentials that are stored in a directory service. This authentication module is pre-configured for LDAP. You can configure a module to use the standard LDAP scheme or LDAPS over SSL.
The LDAP authentication module does not import all of the user accounts from the directory service. Hub only creates a user account when an unregistered user first logs in to Hub or a connected service.
When LDAP authentication is enabled, Hub checks the directory service for each login attempt. Users who have been removed from the directory service cannot log in to Hub.
If you want to connect to the directory service over SSL, import the trusted SSL certificate for your LDAPS server before you enable the authentication module. If there are any intermediate certificates that sit between the SSL certificate and the root CA certificate, you need to upload a file that contains the full certificate chain.
The option to import a trusted SSL certificate is not supported in the settings for the LDAP authentication module. Instead, you need to access the Trusted SSL Certificates page and import it there. For more information, see Trusted SSL Certificates.
Enable LDAP Authentication
To allow users stored in a directory service to log in to Hub, enable an LDAP authentication module.
To enable LDAP authentication:
In the Access Management section of the Administration menu, select .
- From the Add Module drop-down list, select LDAP.
The New Module dialog opens.
- In the New Module dialog, enter values for the following settings:
Enter a name for the authentication module.
Enter the server address of the directory service. For a connection over SSL, change the protocol part of the address to
Enter the number of the port used to communicate with the directory service.
The default port for standard LDAP is
The default port for LDAPS is
Enable this option to connect to the directory service over SSL. Before you can establish a secure connection, you need to import the trusted SSL certificate for your LDAPS server. For instructions, see Trusted SSL Certificates.
Enter the domain components that define the top-level LDAP DN where user accounts are stored. For example, if your company uses the domain
mycompany.com, enter the top-level LDAP DN
The value entered in this field is added to the LDAP URL and cannot contain unsafe characters.
If you use organizational units to manage users, create separate auth modules for each organization. Include the organizational unit in the search base to create a unique LDAP URL for each module. LDAP authentication modules do not support recursive search in the LDAP tree.
- Click the Create button.
The LDAP authentication module is enabled. The current status of the module is displayed next to the name of the module in the header.
The Auth Modules page displays the settings for the LDAP authentication module. The module is pre-configured with standard settings that are based on the information you provided in the Add Module dialog. For additional information about the settings on this page, see the Settings section.
Test the Connection to your Directory Service
To verify that the LDAP authentication module is connected to your directory service, test the connection.
To test the connection:
Click the Test Login button.
- In the Test Authentication dialog, enter the credentials of a user who is stored in your directory service:
In the Login field, enter the
In the Password field, enter the
- Click the Test Login button.
Hub searches for the specified user account in the directory service. If the user is found, a success notification is displayed. If you get an error, check your user credentials and server URL.
Use the following settings to fine-tune the connection to your directory service.
Displays the type of directory service that is enabled for third-party authentication in Hub.
Stores the name of the authentication module. Use this setting to distinguish this module from other authentication modules in the Auth Modules list. The name is also shown in the list of supported authentication providers on the login form.
|Stores the LDAP URL of the directory service used to authenticate a login request in Hub. |
The LDAP URL uses the format
Select an SSL key to encrypt the connection between Hub and the directory service. For more information about managing SSL keys in Hub, see SSL Keys.
Stores an expression that locates the record for a specific user in the LDAP service. The substitution variable in the expression is replaced with the value entered as the username or email on the login page.
|Determines whether the LDAP authentication module ignores or follows requests from the service to locate additional information in the LDAP directory. |
Bind Account Options
You can configure the module to perform the bind request with the LDAP service in one of two ways. The method used is determined by the option selected for the Bind account setting.
The value that you use for the Bind DN setting depends on the option that you select for the Bind account setting. Use the following guidelines to set the value for the Bind DN setting:
Guideline for Bind DN Setting
Uses a fixed account to bind to the LDAP service and searches for the user you want to authenticate on behalf of the bind user. With this option, you can set up an LDAP authentication module and still use logins that are not part of the Distinguished Name (DN), like an email address or token. This method is also commonly called search + bind or two-step authentication.
Enter the full DN of the user account that you want to use for the LDAP bind request. This account must have permission to look up other user accounts in the directory service.
Derives the user DN from the login and attempts to bind to the LDAP service as the user directly. This method is also commonly called direct bind.
Use a query to bind with the directory service. This query looks up the distinguished name of the user to be authenticated. Reference the username with an expression. The expression maps a substitution variable to the attribute that stores the username in the directory service. The attribute you select determines which query is used in the filter string.
When Hub finds a record in the LDAP service that matches a filter, it fetches values from the LDAP attributes that are specified for each field and copies them to the user profile in Hub. Use the following settings to define the filter criteria and map attributes that are stored in your directory service to user accounts in Hub.
|Required. Maps to the LDAP attribute that stores the value to copy to the Login field in the Hub profile. For LDAP, the default value is |
Maps to the LDAP attribute that stores the value to copy to the Full name field in the Hub profile.
Maps to the LDAP attribute that stores the value to copy to the Email field in the Hub profile.
Maps to the LDAP attribute that stores the value to copy to the Jabber field in the Hub profile.
VCS user name
Maps to the LDAP attribute that stores the value to copy to the VCS user name field in the Hub profile.
The following options are located at the bottom of the page. Use these settings to manage Hub account creation, group membership, and connection options.
|Enables creation of Hub accounts for unregistered users who log in with an account that is stored in the connected directory service. Hub uses the email address to determine whether the user has an existing account. |
All LDAP authentication modules must allow user creation. If user creation is denied, unregistered users are shown an error.
Adds users to a group when they log in with an account that is stored in the connected directory service. You can select one or more groups. New users that auto-join a group inherit all of the permissions assigned to this group.
Sets the period of time to wait to establish a connection to the authorization service. The default setting is 5000 milliseconds (5 seconds).
Sets the period of time to wait to read and retrieve user profile data from the authorization service. The default setting is 5000 milliseconds (5 seconds).
Links to the Audit Events page in Hub. There, you can view a list of changes that were applied to this authentication module.
On the Group Mappings tab, you can map existing groups in the LDAP service to the groups in Hub.
If you want to map LDAP groups to Hub groups, you need to specify the Groups attribute that stores LDAP group memberships in the Attribute Mapping section of the settings for this auth module.
When group mappings are configured, Hub checks for LDAP group memberships when users log in with accounts that are managed in the directory service. Hub performs the following operations for each LDAP group that is mapped to a Hub group:
Users who are members of a mapped LDAP group and are not members of the mapped Hub group are added to the group in Hub.
Users who are not members of a mapped LDAP group and are members of the mapped Hub group are removed from the group in Hub.
Changes to group memberships in the LDAP service are only applied in Hub when users log in using the LDAP auth module.
You can map multiple LDAP groups to a single target group in Hub. You can't map LDAP groups to more than one Hub group.
To map an LDAP group to a group in Hub:
Open your LDAP auth module.
Select the Group Mappings tab.
- Click the Add mapping button.
The Add Mapping dialog opens.
- Enter the name of the LDAP group in the LDAP group name field.
If the Bind account option is set to Fixed, the auth module uses the bind account look up groups in the directory service. Available groups are shown in the LDAP group name list.
If the Bind account option is set to Dynamic, the list of groups in the directory service is not available to the bind account. To map a group successfully, you need to enter the name of the group exactly as it appears in the directory service.
Select a group from the Hub group list.
- Click the Add button.
The mapping is added to the list.
Use the following patterns to configure an LDAP auth module using the LDAP protocol:
Use the following patterns to configure an LDAP auth module with a secure connection over SSL: