After you have created your plug-in, configure Access Manager to use it.
Copy the plug-in class file to Identity Server:
Copy it to the following directory 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 you want to use a LDAP-plugin class file: C:\Program Files (x86)\Novell\Tomcat\webapps\nidp\WEB-INF\classes
If you want to use a LDAP-plugin class in a jar file: C:\Program Files (x86)\Novell\Tomcat\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.
Repeat Step 1.a for each Identity Server in the cluster.
To associate an LDAP Server plug-in with the Custom1, Custom2, or Custom3 directory type, modify the web.xml file on Identity Server:
In a text editor, open the following file:
Windows: C:\Program Files (x86)\Novell\Tomcat\webapps\nidp\WEB-INF\web.xml
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 following format:
In Administration Console, configure Identity Server to use the new directory type for a user store.
Click> > > .
Either select the name of a user store or click.
For the Step 2., select the custom string you have configured in
Complete one of the following:
For a new user store, configure the other required values, then click.
For a modified user store, modify the other options to fit the new directory type, then click.
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.