As a Federal Partner, I want to understand how CONNECT's certificate configuration impacts FIPS 140-2 compliance.

Description

See for more details on CONNECT's certificate configuration.

CONNECT currently references keystores and truststores via the file system. Determine the impact of this functionality per FIPS 140-2 requirements. Does this necessitate a change like the one listed in CONN-340?

There is a good two part write up about doing FIPS with CXF using the NSS libraries (GlassFish beware!):

http://davidvaleri.wordpress.com/2010/10/19/using-nss-for-fips-140-2-compliant-transport-security-in-cxf/
http://davidvaleri.wordpress.com/2010/12/16/using-nss-for-fips-140-2-compliant-message-security-in-cxf/

REMINDER: GlassFish 3.x does not support the NSS libraries, as of April 2013.

Resolution Details

None

Assignee

Unassigned

Reporter

msweaverN

Labels

LOE

Unknown

Reporting Organization

SSA

Fix versions

Affects versions

Priority

Minor
Configure