/mcpLikewise, having the Unified CM operate in FIPS mode will not make JTAPI store certificates with FIPS-compliant algorithms. They are distinct items, separated by a”cryptographic boundary.” Also, even if JTAPI operates in FIPS-compliant mode, your application may not. Your applications must handle cryptographic information and other sensitive data with special attention to be FIPS-compliant. As mentioned earlier, applications that need to use FIPS compliance must not only explicitly request it, but also download cryptographic libraries and modify their classpath variables to include them. Until Unified Communications Manager Release 12.5(1), JTAPI used RSA libraries for FIPS-compliant operations. With Release 12.5(1) and later, JTAPI on Windows uses RSA libraries, while on Linux it uses CiscoJ libraries. As of Unified Communications Manager Release 14SU2, JTAPI uses BCFIPS libraries for all security-related operations. If configured to operate in FIPs mode, JTAPI moves BCFIPS libraries to approved only mode to enforce FIPS compliance. The libraries are detailed below: The RSA libraries are: “jcmFIPS.jar” “cryptojcommon.jar”, “ cryptojce.jar” and “sslj.jar”, are FIPS-compliant libraries from RSA, Inc. The CiscoJ libraries are: The CiscoJ libraries are “CiscoJCEProvider.jar”, “log4j-1.2.17.jar”, “slf4j-api-1.7.24.jar”, “slf4j-log4j12-1.7.24.jar”, “slf4j-simple-1.7.24.jar”, “bcpkix-jdk15on-154.jar”, and “bcprov-jdk15on-154.jar”. From Release 12.5(1)SU5 on this train and up to 14SU1, “bcpkix-jdk15on.jar” and “bcprov-jdk15on.jar” are used instead of “bcpkix-jdk15on-154.jar” and “bcprov-jdk15on-154.jar” respectively. Note From Release 14SU2 to 15SU1, the BCFIPS libraries are: • bc-fips.jar (version 1.0.2.3) • bctls-fips.jar (version 1.0.12.3) • bcpkix-fips.jar (version 1.0.5) Note Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 96 Features Supported by Cisco Unified JTAPI FIPS Compliance