BMC ar configuration area LDAP

Ar uses plug-ins for external authentication. When installing AR, it comes with plug-in services and installs some built-in plug-ins, such as area and ardbc. The interaction between the main ar service and the plug-in is mainly completed through the plug-in service. At the same time, the AR plug-in service has a complete API, which can be used by a third party to develop custom plug-ins.

During the last deployment of area LDAP, the configuration never takes effect. After arduous troubleshooting, the cause was finally found.

First, let's take a look at how to configure the area:

Server Information-> EA

The configuration is simple, but the problem is that it does not work. The following are difficult troubleshooting experiences:

1. install network monitor on the AR server and check whether there is an LDAP request package. If there is a request package in this step, it is estimated that there is a problem with the BIND user configuration, either the user name does not have the query permission, or the password is incorrect or has expired.

2. Without LDAP data packets, I checked whether the LDAP information configured in the AR. cfg file is consistent with that set on the interface. Once upon a time, I found a piece of LDAP-hub configuration, which can be deleted after being deleted. Check the document, saying that area LDAP supports configuring multiple LDAP configurations in the hub mode. It is assumed that the configuration file is not updated because there are too many LDAP configurations in the area.

3. Check whether ar. cfg is correct. Check the document, enable the log function of Ar-plugin, restart AR, and find that the plug-in of area is not loaded at all. View the plug-in configuration in Ar. cfg and find that areaplugin. dll is not configured! Add a record manually and restart ar.