The first thing you must do is determine whether or not your Camunda server can access the LDAP port on the LDAP server. For example, if your LDAP server was called myldaphost.company.com, then you can determine this using the following command (assumes you have access to the "telnet" utility on your Camunda server):
telnet myldaphost.company.com 389
Port 389 is the standard, non-SSL port for LDAP. If you are trying to use SSL, the standard port is 636. SSL is much harder to configure, by the way. I noticed in my own original WildFly configuration, that the LDAP configuration section (which is commented out as we don't use it) contains a "serverUrl" of "ldaps://localhost:4334" This implies that they expect you to be running an LDAP server on the same host as Camunda and at a non-standard port. Typically, LDAP would be provided by a separate server maintained within your company.
It's important to note that sometimes the LDAP server is supported by a Windows Active Directory server, which provides both Active Directory and LDAP services. You should ask your system administrators about it. If no LDAP server exists within your organization, then you're going to have to set one up yourself. I would question whether this makes sense.
I am not an LDAP expert and quite frankly get confused by some of the configuration requirements. However, if basic connectivity to the LDAP host is an issue, the technique above will confirm it.
Once you have established that you can access the LDAP service, you will need to obtain some information from your LDAP administrators to complete the configuration. In the Camunda WildFly distribution, the LDAP configuration section in the standalone.xml file is commented out. I'm sure there's a similar configuration section for Tomcat and other Java application servers. Within that section you will find a bunch of attributes you will need to set properly for this to work. Unfortunately, I can't help you much there.