To get started with the integration, deploy the RSA SecurID Integration Kit files to your PingFederate directory.
- Download the RSA SecurID Integration Kit .zip archive from the Ping Identity Integration Directory.
- Stop PingFederate.
-
If you are upgrading an existing deployment, back up your customizations and
delete older versions of the integration files.
-
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
-
Delete the following from
<pf_install>/pingfederate/server/default/deploy:
- pf-rsa-securid-idp-adapter-<version>.jar
-
Back up any RSA SecurID Integration Kit files that you customized
in
<pf_install>/pingfederate/server/default/conf/templates:
- Extract the .zip archive and merge the contents of the dist directory with your <pf_install>/pingfederate directory.
-
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.
- 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.
- Start PingFederate.
- If you operate PingFederate in a cluster, repeat steps 2-7 for each engine node.