Install Guide

Binary Installation for Android 15
RSA BSAFE Cert-J 6.2.4 Installation Guide
4. If you do not wish to use a Native FIPS or Native non-FIPS configuration of
Cert-J, go to Step 6.
To use a Native FIPS or Native non-FIPS configuration of Cert-J, the
Crypto-C ME platform-specific shared libraries must be added to the Java library
path. The following table details the subdirectories in
<root>/certj/prebuilt/cryptocme
that contain the platform-specific
shared libraries.
5. Select the Native shared library
.so files to use and copy them to the specified
directories:
Note: In the following instructions, replace platform with either x86 or
armeabi-v7a as applicable.
– To work with Cert-J configured as non-FIPS 140-2 compliant, copy
libncm.so to the platform-specific folder for the shared native library files
in the Android project at
/jniLibs/platform/android-project or
/libs/platform/android-project.
– To work with Cert-J configured as FIPS 140-2 compliant:
• Copy the following shared libraries to the platform-specific folder for the
shared native library files in the Android project at
/jniLibs/platform/android-project or
/libs/platform/android-project:
• Copy the signature file,
libcryptocme.sig, to the
android-project
/assets/platform directory.
For details about how to use Native configurations of Cert-J, see the API-specific
section “Using Native Implementations” in the RSA BSAFE Cert-J Developers
Guide.
6. To use the Crypto-J JsafeJCE API, dynamically register the Crypto-J JCE
provider, JsafeJCE:
a. Add the relevant jar files to the class path.
Table 9 Platform-specific Crypto-C ME Native Shared Library subdirectories
Platform
Subdirectory
Google Android 32-bit
android_x86
Google Android ARM
®
v7
android_armv7
• libccme_asym.so • libccme_ecc_accel_fips.so
• libccme_aux_entropy.so • libccme_ecc_accel_non_fips.so
• libccme_base.so • libccme_ecdrbg.so
• libccme_base_non_fips.so • libccme_error_info.so
• libccme_ecc.so • libcryptocme.so
• libccme_ecc_non_fips.so • libncm_fips140.so