Customize the AM WAR file

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

To customize the secure cookie filter, refer to Secure cookie filter.

You can also customize the AM user pages and package them into the WAR file.

For more information about the customizations to include in the WAR file, refer to Customize before upgrading.

Enable RSA SecurID support

To use the SecurID authentication module, you must first build an AM WAR file that includes the supporting libraries, authapi.jar and crypto.jar, which you must obtain from RSA.

Unpack the AM .war file. For example:

$ mkdir /tmp/openam
$ cd /tmp/openam/
$ jar -xf ~/Downloads/openam/AM-7.5.0.war

Obtain the authapi.jar and its dependency file, crypto.jar from RSA.

Copy authapi.jar into the WEB-INF/lib directory.

For example:
```
$ cp /path/to/authapi-<VERSION>.jar WEB-INF/lib/
```
Pack up the AM .war file. For example:
```
$ jar -cf ../openam.war *
```
Deploy the new .war file. For more information, see Deploy AM.

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

PingAM 7.5.0

Customize the AM WAR file

Enable RSA SecurID support