Troubleshooting AREA Hub plug-in issues


AR System plug-in server supports only one AR System external authentication (AREA) plug-in directly. You can, however, add a single AREA Hub plug-in to the plug-in server and then add multiple AREA plug-ins to the AREA Hub plug-in.

Plug-ins that are added to the AREA Hub are referred to as Hub plug-ins. The AREA Hub transmits the calls it receives from the Hub plug-ins to the plug-in server.

Plug-in type

AREA Hub is a C-based AREA plug-in.

AR System server connectivity

AR System server interacts with the AREA Hub plug-in when an event occurs on the LDAP Configuration form.

The AREA Hub plug-in is installed in the following location:

  • (Microsoft Windows) <ARInstallationFolder>\arealdap\areahub.dll
  • (UNIX) <ARInstallationFolder>/arealdap/areahub.so

Configuration information

The AREA Hub plug-in is configured in the AR System Administration: AR System Configuration Generic UI form.

You need not configure the AREA Hub manually to use multiple AREA LDAP plug-ins.

Important

If you are using the Java-based AREA LDAP plug-in, the Java plug-in server automatically performs the chaining of the AREA plug-ins in the order in which they appear in the AR System Administration: Plugin Server Configuration form.

To troubleshoot AREA LDAP plug-in issues

  1. Verify the AREA Hub plug-in configuration.
  2. On the server, verify that the plug-in resides in the directory listed and that permissions are consistent with the user who executed arserver.exe (arserverd). This information is important if you perform installation as a non-root user.
  3. Restart AR System server.
    To restart the plug-in server without restarting AR System server, see Restarting-the-plug-in-server.
  4. To further investigate the issue, enable the server-side logs and plug-in logs.
    For instructions, see Setting-log-files-options.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*