Symantec VIP Integration Kit

Known issues and limitations

The following are known issues or limitations for the Symantec VIP integration kit.

Known issues

WebAppContext context path isn’t set correctly if file type is a .war directory:

If you modify the contents of the .war directory in the integration kit with custom assets and set a custom context path in your PingFederate runtime environment, the integration kit doesn’t set the correct context path for the web application. This is because .war is a directory in the integration kit instead of a file, like it is in PingFederate.

The current workaround for this issue is to modify the applicable assets paths for the adapter’s .jsp files with the context path that you want to use. Then, create a .war file containing the custom assets.

To create a .war file:

  1. In the command line, go to the vip-adapter-security-code-challenge.war directory that contains your changes.

  2. Run the following command:

    jar -cvf vip-adapter-security-code-challenge.war *

    This step assumes that your Java Development Kit’s bin directory is part of your command line path.

  3. Copy the resulting vip-adapter-security-code-challenge.war file into the <pf_install>/pingfederate/server/default/deploy directory.

  4. In the <pf_install>/pingfederate/server/default/deploy directory, delete any previous versions of the vip-adapter-security-code-challenge.war directory.

  5. To set the context paths in the .war file correctly, perform a restart.

    Repeat these steps whenever you want to make changes to the contents of the .war file.

Known limitations

There are no known limitations.