Active Directory Cookbook

4.4. Using a Fast or Concurrent Bind

Problem

You want to perform an LDAP bind using a concurrent bind, also known as a fast bind. Concurrent binds are typically used in situations where you need to authenticate a lot of users, but those users do not need to directly access the directory or the directory access is done with another account.

Solution

Tip

This works only on a Windows Server 2003 domain controller.

Using a graphical user interface

1. Open LDP.

2. From the menu, select Connection → Connect.

3. For Server, enter the name of a DC.

4. For Port, enter 389.

5. Click OK.

6. From the menu, select Options → Connection Options.

7. Under Option Name: select LDAP_OPT_FAST_CONCURRENT_BIND

8. Click the Set button

9. From the menu, select Connection → Bind.

10. Enter credentials of a user.

11. Click OK.

Discussion

Concurrent binding, unlike simple binding, does not generate a security token or determine a user’s group memberships during the authentication process. It only determines if the authenticating user has a valid enabled account and password, which makes it much faster than a typical bind. Concurrent binding is implemented as a session option that is set after you establish a connection to a domain controller, but before any bind attempts are made. After the option has been set, any bind attempt made with the connection will be a concurrent bind.

There are a couple of caveats when using concurrent binds. First, you cannot enable signing or encryption, which means that all data for concurrent binds will be unencrypted over ...