PingAccess

Managing Federal Information Processing Standards (FIPS) mode

Federal Information Processing Standards (FIPS) mode ensures that PingAccess uses encryption algorithms that meet FIPS requirements.

View your environment’s FIPS mode status

If FIPS mode is enabled, you can view your environment’s FIPS mode status in the PingAccess admin console or audit log:

  • To view FIPS mode in the admin console, go to Account > About and in the System Information section, find FIPS mode status.

  • To view FIPS mode in the audit log, review the audit log after starting PingAccess. If FIPS mode is enabled, an info-level entry indicates this status. For example:

    INFO [] Fipsconfig - PingAccess is currently running in FIPS Mode.
Feature changes in FIPS mode

Some features of PingAccess operate differently or are unavailable in FIPS mode.

Features that aren’t supported in FIPS mode:

  • SHA-1

  • PKCS#12 certificates and private keys

Certificate and private key format requirements:

  • PingAccess only supports PEM-formatted certificates and private keys, meaning:

    • You can only import or export key pairs using the PEM-encoded format.

    • PingAccess only accepts PBES2 and AES or Triple DES encryption.

    • PingAccess requires 128-bit salt.

      In practice, this could mean that you can only import PEM files generated by PingFederate.

  • For PEM files, the private key must precede the certificates.

Password format requirements:

  • The password must contain at least 14 characters.

To manage FIPS mode, select a tab.

  • Enabling FIPS mode

  • Disabling FIPS mode

Enabling FIPS mode

About this task

Enable FIPS mode to ensure that PingAccess exclusively uses encryption algorithms permitted by the FIPS standard. If your environment is clustered, make sure to perform this procedure on all nodes.

In this procedure, you can manually specify security providers, TLS protocols, and TLS cipher suites that can be used. If your manual inclusions are not FIPS-compliant, your environment might not be FIPS-compliant even in FIPS mode.

Steps

  1. Open the <PA Home>/conf/fips-mode.properties file or create it if it’s been removed.

  2. Set the pa.fips.mode property to true.

    Example:

    pa.fips.mode=true

  3. (Optional) Exempt one or more security providers from being excluded by FIPS mode by adding a comma-separated list of class names to the pa.fips.additionalAllowedProviders property.

    Example:

    pa.fips.additionalallowedproviders=X,Y

  4. (Optional) Add or remove TLS protocols by editing the pa.fips.tls.protocols property to include a comma-separated list of valid TLS protocols.

    The default is:

    pa.fips.tls.protocols = TLSv1.2

  5. (Optional) Add or remove TLS cipher suites by editing the pa.fips.tls.ciphers property to include a comma-separated list of valid TLS cipher suites.

    The default is:

    pa.fips.tls.ciphers = TLS_AES_256_GCM_SHA384, \
                      TLS_AES_128_GCM_SHA256, \
                      TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, \
                      TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, \
                      TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, \
                      TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, \
                      TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, \
                      TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, \
                      TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, \
                      TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, \
                      TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, \
                      TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, \
                      TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, \
                      TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, \
                      TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, \
                      TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, \
                      TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, \
                      TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, \
                      TLS_EMPTY_RENEGOTIATION_INFO_SCSV

    Some of the default cipher suites aren’t supported by every JDK version that can be used with PingAccess. If a TLS cipher suite isn’t supported by the JDK version you’re using, PingAccess will log a warning in the pingaccess.log file when the cipher suite is invoked.

    PingAccess can ignore any flagged TLS cipher suites with no performance impact. To clear the warning message, you can remove the flagged suites from the pa.fips.tls.ciphers property.

  6. Save and close the <PA Home>/conf/fips-mode.properties file.

  7. If you’re running PingAccess as a Windows service, reconfigure the classpath for the libraries required for FIPS mode:

    1. Comment out the following line:

      set.default.BC_PATH=../../resource/bc/non-fips

    2. Uncomment the following line or set a BC_PATH environment variable to ../../resource/bc/fips:

      # set.default.BC_PATH=../../resource/bc/fips

    Learn more in the inline comments in the <PA_HOME>/sbin/windows/PingAccessService.conf file.

  8. Restart PingAccess.

Disabling FIPS Mode

About this task

Disable FIPS Mode to allow the use of non-FIPS compliant encryption. If your environment is clustered, perform this procedure on all nodes.

Steps

  1. Open the <PA Home>/conf/fips-mode.properties file.

  2. Set the pa.fips.mode property to false.

    pa.fips.mode=false

  3. Save and close the <PA Home>/conf/fips-mode.properties file.

  4. If you’re running PingAccess as a windows service, reconfigure the classpath for the libraries required for FIPS mode:

    1. Uncomment the following line:

      # set.default.BC_PATH=../../resource/bc/non-fips

    2. Comment out the following line or the BC_PATH environment variable to ../../resource/bc/fips that you set:

      set.default.BC_PATH=../../resource/bc/fips

    Learn more in the inline comments in the <PA_HOME>/sbin/windows/PingAccessService.conf file.

  5. Restart PingAccess.