Load Testing Your LDAP With JMeter Part 1

JMeter is a powerful load testing utility supporting many different types of servers and protocols including HTTP, JDBC, LDAP, and TCP. This blog post will walk you through load testing an LDAP server.

If you’d like to follow along, you should download and install JMeter before you begin. This open source tool and is freely available here.

In part 1, we will look at configuring JMeter to do a few simple operations against an LDAP. We will also introduce a multithreaded test feature to simulate many concurrent operations.


Setting Up Your Test Plan

When you first launch JMeter, you will find an empty test plan. To add components to your test plan, right click on the tree and choose to choose Add, and then select the appropriate Test Element, Processor, Listener, etc.

To start, add a Thread Group to your test plan. This will allow your test to execute several threads concurrently. Accept the default settings for now.


Next, right click on the Thread Group and add a Loop Controller (under Logic Controllers), and accept the default settings.

Now right click on the Loop Controller, choose Add, and then select LDAP Extended Request from the Sampler list. You will see this new node in the tree under the Loop Controller. Finally, we need a way to view the progress of our test, so we need to add a listener. Right click on the Loop Controller once again, and select Add -> Listener -> View Results in Table.

Your test plan should look like this:


Next you will need to fine-tune the LDAP Request. For this example, let’s use a simple Bind/Unbind. You can also increase the number of threads from 1 to 10, 50, 100 or more.



Executing Tests

Before you start testing, be sure to save your test plan. Executing your test plan is simple: from the Run menu, click Start. You can also use the menu bar (the green Start button) or use CTRL+R.

While your tests are executing, you can select the View Results in Table Listener under your test plan to view progress and stats.



This is simply a starting point. We encourage you to experiment with different samplers, controllers, and listeners to fine-tune your test to meet your specific needs. And as always, we encourage you to reach out to the experts here at IDMWORKS who can help develop your comprehensive performance testing strategy.

Stay tuned in the coming weeks for Part 2 where we will show you how to distribute your load test across multiple nodes as well as how to use a CSV data set for test users.

Questions, comments or concerns? Feel free to reach out to us below, or email us at IDMWORKS to learn more about how you can protect your organization and customers.