BuildMaster can use any existing LDAP infrastructure. This guide will help
you get the system set up.
Add LDAP Users to BuildMaster
Before switching BuildMaster over to LDAP authentication, you must first
configure which LDAP users or groups will have permission to use BuildMaster.
First, click on the Privileges link under Security
& Permissions on the BuildMaster Administration
You will be presented with a list of Principals currently recognized by
BuildMaster. Click the directory filter and set it to show LDAP Principals:
Next, click the Add Privilege button and the Add Privilege
dialog will be displayed. To ensure that you will be able to access BuildMaster
after switching it over to LDAP, you may want to add your current LDAP user
account and assign the BuildMaster role (BuildMaster
is essentially an administrator):
After clicking the Save button, your LDAP user account/group
should now be listed as a Principal in BuildMaster. You are now ready to switch
the directory provider over to LDAP.
To integrate with Active Directory, BuildMaster's web site in IIS must be
configured to use Windows Authentication and to
disable Anonymous Authentication. Upon installation, a
BuildMaster web site will be created in IIS. To configure Windows Authentication
on this site, follow the appropriate guide:
Enabling LDAP Integration
Click the Directory link under Integration
Configuration on the BuildMaster Administration Page.
Now, select LDAP from the Directory Provider
Now just click Save Changes and BuildMaster will start using LDAP.
If you have set LDAP as your directory provider in BuildMaster and can no
longer access it, you can go back to integrated authentication in one of two ways:
The easiest way is to use the BuildMaster Admin Tool, located in the "Service" subdirectory of the
BuildMaster installation directory. Simply run the "BuildMaster.Configuration.AdminTool.exe" tool from
the server that hosts the BuildMaster application and you can switch the directory provider.
You may also switch the provider by executing the
following script against the BuildMaster database (for example, using SQL Server
USE BuildMasterUPDATE [Configuration]
SET [Value_Text] = '1'
WHERE [Scope_Name] = 'CoreEx'
AND [Key_Name] = 'DirectoryProvider'
This will make BuildMaster accessible again, allowing you to correct the
This content has the following tags: