Customizing the AM WAR File

The most basic installations of AM do not require you to customize the AM WAR file file before deploying it. However, if you need to customize any of AM extension points, you should add the new classes to the WAR file before deploying it.

Tip

To customize the secure cookie filter, see "Managing the Secure Cookie Filter".

You can also customize the AM user pages and package them into the WAR file. For more information, see UI Customization Guide

Enabling RSA SecurID Support

To use the SecurID authentication module, you must first build an AM WAR file that includes the supporting library, for example authapi-2005-08-12.jar, which you must obtain from RSA. The authapi-2005-08-12.jar file also requires a dependency file, crypto.jar, which you can also obtain from RSA.

  1. Unpack the AM .war file. For example:

    $ mkdir /tmp/openam
    $ cd /tmp/openam/
    $ jar -xf ~/Downloads/openam/AM-7.0.2.war
  2. Obtain the authapi.jar (for example, authapi-2005-08-12.jar) and its dependency file, crypto.jar from RSA. Then, copy authapi-2005-08-12.jar into the WEB-INF/lib directory. For example:

    $ cp /path/to/authapi-2005-08-12.jar WEB-INF/lib/
  3. Pack up the AM .war file. For example:

    $ jar -cf ../openam.war *
  4. Deploy the new .war file. For more information, see Deploying AM.

    In this example, the .war file to deploy is /tmp/openam.war.

Read a different version of :