This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

Troubleshooting AREA LDAP plug-in issues

The AR System External Authentication (AREA) LDAP plug-in enables you to authenticate BMC Remedy AR System users against external LDAP directory services. The AREA LDAP plug-in implements the AREA LDAP Configuration form.

Plug-in type

AREA LDAP is a Java-based plug-in.

AR System server connectivity

The AR System server interacts with the AREA LDAP plug-in when an event occurs on the AREA LDAP Configuration form. This plug-in (arealdappluginVerNum.jar) is installed in the <ARInstallationFolder>\pluginsvr directory. ( — VerNum represents the release version number).

Configuration information

The configuration information of the AREA LDAP plug-in is available in the <ARInstallationFolder>\pluginsvr\pluginsvr_config.xml file that includes the plug-in details in XML code as follows:

<plugin>
 <name>ARSYS.AREA.AREALDAP</name>
 <pathelement type="location">D:/Program Files/BMC Software/ARS801/pluginsvr/arealdapplugin81_build001.jar</pathelement>                                        <classname>com.bmc.arsys.plugins.arealdap.AREALdapPlugin</classname>
</plugin>

The ar.cfg/ar.conf file includes the Server-Plugin-Alias setting that points to the correct plug-in server alias as follows:
Server-Plugin-Alias: AREA AREA myServer:9999

There is no separate Server-Plugin-Alias for each AREA type of plug-in.

If you have a custom AREA LDAP plug-in that is developed in C, you need to use the native plug-in server instead of the Java plug-in server. This fallback can be configured in the pluginsvr_config.xml file and is controlled by a property called enableNativeBridge. This property routes the AREA login verification calls to the native plug-in server.

By default, the value of enableNativeBridge property is false, meaning the native plug-in server is not available. To enable this property, edit the pluginsvr_config.xml file and add the following code under the pluginsvr_config tag:

<pluginsvr_config>
<enableNativeBridge>true</enableNativeBridge>

If the enableNativeBridge property is enabled, during AREA login verification, the Java plug-in server chains through all the Java AREA plug-ins in the order in which they appear in the pluginsvr_config.xml file. If no match is found, the call is propagated to the native plug-in server to check the AREA plug-ins hosted by the native plug-in server.

To avoid infinite looping between the Java plug-in server and the native server, ensure that you have disabled the AREA Proxy plug-in (areaatriumsso.dll) after enabling the enableNativeBridge property.

To troubleshoot AREA LDAP plug-in issues

  1. Verify the AREA LDAP plug-in configuration.
  2. Troubleshoot common plug-in related issues.
    For more information, see General approach for troubleshooting plug-in issues.
  3. If you need to investigate the issue further, enable the following logs:

To enable logging for the AREA LDAP plug-in

  1. Modify the following lines in the <ARInstallationFolder>/pluginsvr/log4j_pluginsvr.xmlfile:

    <logger additivity="true" name="com.bmc.arsys.pluginsvr.plugins">
     <level value="warn"/>
    </logger>
    

    to

    <logger additivity="true" name="com.bmc.arsys.pluginsvr.plugins">
     <level value="debug"/>
    </logger>
    
  2. Restart the AR System server.
    The arjavaplugin.log file now generates the debug logging for the AREA LDAP plug-in.

Related topics

Using the AREA LDAP plug-in
Configuring the AREA LDAP plug-in

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments