000011534 - How to set up the RKM Java Client lockbox

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011534
Applies ToRKM Java Client
IssueRKM Java Client: How to set up the lockbox
Resolution

Refer to the RKM Java Client Installation Guide, "To install the Lockbox (optional):" section.  Here are some additional details.
1. Ensure that the directory where the cryptographic libraries used by the lockbox (e.g. cryptocme2.dll or libcryptocme2.so) are located is in the system's PATH environment variable (PATH on Windows, LD_LIBRARY_PATH on Solaris and Linux, SHLIB_PATH on HP-UX, and LIBPATH on AIX (http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html) or if you are using an application server, ensure that the libraries are somewhere in the path that the application server is looking (e.g. lib directory).
(In releases up through RKM Java Client 2.7.1.3 / DPM Java Client 3.1, this step is missing from the documentation.  Bugs have been filed.)



2. Set the java.library.path property to point to the directory containing the libraries
required for the Lockbox software:


To do this in the sample build.xml file, you can add this line such as this (where "C:\cst_2.0\bin" is the directory containing the libraries
required for the Lockbox software):


            <sysproperty key="java.library.path" value="C:\cst_2.0\bin;${java.library.path}" />
           


to the "run" target:


    <target name="run" depends="compile,-check.class.name">
        <java classname="${class.name}"
            fork="true"
            failonerror="true">
            <classpath>
                <path refid="common.libs" />
                <path location="${classes.dir}" />
            </classpath>
            <sysproperty key="log4j.configuration" value="file:${testdata.dir}/log4j.properties"/>
            <sysproperty key="log.dir" value="${log.dir}"/>
            <sysproperty key="kmjc.version" value="${dot.version}" />
           
            <sysproperty key="java.library.path" value="C:\cst_2.0\bin;${java.library.path}" />
                       
        </java>
    </target>



3. Copy LB.jar and LBImpl.jar from <cst install dir>/java to <install dir>/rkmc/lib .
Make sure these two .jar files are on the CLASSPATH.


4. Set these properties in <install_dir>/rkmc/testdata/sample_config.properties:


  client.lockbox=true


  # Admin Password for creating the LockBox.Passphrase should be 8 or more characters in length, contain
  # at least one numeric, one uppercase and lowercase, one non-alphanumeric character such as # or !
  client.lockbox_admin_password=<lockbox password>


 


The client registration file will be rewritten and contain base64 encoding (of encrypted values) that looks like this;


3.000000|QFByb2R1Y3Rpb24gbW9kZSBzZXQsIGZpbGUgY29udGVudHMgZW5jcnlwdGVkIQoxMDAsMjI
...


The following files are created:


<registration filename>.FCD
- contains # characters



<registration file name>.state
- contains timestamp and client.lockbox_state


  #
  #Thu Mar 29 16:17:12 PDT 2012
  client.lockbox_state=true



<registration file name>.bak
<registration file name>.bak.FCD

Legacy Article IDa57819

Attachments

    Outcomes