1. Download the RSA SecurID Integration Kit .zip archive from the Ping Identity Integration Directory.
  2. Stop PingFederate.
  3. If you are upgrading an existing deployment, back up your customizations and delete older versions of the integration files.
    1. Back up any RSA SecurID Integration Kit files that you customized in <pf_install>/pingfederate/server/default/conf/templates:
      • RSASecurIDIdPAdapter.form.template.html
      • RSASecurIDIdPAdapter.nexttoken.template.html
      • RSASecurIDIdPAdapter.reauthenticate.template.html
      • RSASecurIDIdPAdapter.systempinreset.template.html
      • RSASecurIDIdPAdapter.userpinreset.template.html
      • RSASecurIDIdPAdapter.approve.template.html
      • RSASecurIDIdPAdapter.cas.approve.template.html
      • RSASecurIDIdPAdapter.token.template.html
    2. Delete the following from <pf_install>/pingfederate/server/default/deploy:
      • pf-rsa-securid-idp-adapter-<version>.jar
  4. Extract the .zip archive and merge the contents of the dist directory with your <pf_install>/pingfederate directory.
  5. If you have existing customizations, manually modify the new rsa-securid-messages.properties file based on your previous customizations.

    For more information on customizing messages, see Localizing messages for end users in the PingFederate documentation.

  6. If there is more than one version of the pf-authn-api-sdk-<version>.jar file in your <pf_install>/pingfederate/server/default/lib directory, delete all but the latest version of the file.
  7. Start PingFederate.
  8. If you operate PingFederate in a cluster, repeat steps 2-7 for each engine node.