The TruValidate Multifactor Authentication Service SDKs allow for the use of separate keys
for encryption and signing. While this is an optional step, separate keys for encryption and
signing is a hard requirement to comply with FIPS 140 standards in the event of working
within a FIPS 140 compliant organization (more info here: AAL2 FIPS Compliance).
Configuring a Factory to Utilize Single Purpose Keys
In order to utilize single purpose keys within the SDKs, a factory may be instantiated with
multiple keys, as shown below. While this is an optional step, separate keys for encryption
and signing is a hard requirement to comply with FIPS 140 standards. You can read more about
FIPS compliance here AAL2 FIPS Compliance.
TransUnion links to user contributed code as a resource to its
community. TransUnion does not in any way guarantee or warrant
the quality and security of these code bases. User contributed code is supported by the
creators. If you do find a link from the site to user contributed code that is malicious or inappropriate in any
way, please report that link to TransUnion immediately and we will investigate the claim. Submit any issue to
TransUnion support at https://transunion.com/support.