After you have created your plug-in, configure Access Manager to use it.
Add the plug-in class file to Identity Server to the following directory using Advanced File Configurator under the correct directory structure as per the class package:
If you want to use a LDAP-plugin class file: /opt/novell/nam/idp/webapps/nidp/WEB-INF/classes
If you want to use a LDAP-plugin class in a jar file: /opt/novell/nam/idp/webapps/nidp/WEB-INF/lib
If your class package name is com.acme.ldap.plugin, you need to create the com, acme, ldap, and plugin directories.
For information about how to add a file, see Adding Configurations to a Cluster in the NetIQ Access Manager 5.0 Administration Guide.
To associate an LDAP Server plug-in with the Custom1, Custom2, or Custom3 directory type, modify the Identity Server web.xml file.
Open the web.xml file.
For information about how to modify a file, see Modifying Configurations in the NetIQ Access Manager 5.0 Administration Guide.
Add an entry for the ladpStorePlugins context parameter. Your entry should look similar to the following to associate the com.acme.plugin.Sample1Plugin with the Custom1 directory type.
<context-param> <param-name>ldapStorePlugins</param-name> <param-value>custom1:com.acme.ldap.plugin.Sample1Plugin</param-value> </context-param>
You can add up to three values using the custom1:classname;custom2:classname;custom3:classname format.
In Administration Console, configure Identity Server to use the new directory type for a user store.
Click Access Manager > Identity Servers > Edit > Local.
Either select the name of a user store or click New.
For the Directory type, select the custom string you have configured in Step 2.
Complete one of the following:
For a new user store, configure the other required values, then click Finish.
For a modified user store, modify the other options to fit the new directory type, then click OK.
Update Identity Server.
(Optional) To verify that the new directory type is functioning correctly, log in to the user portal by using the credentials of a user in the user store.
If you encounter any errors, see Section 3.5, Troubleshooting.