To import a certificate and key into an internal PKCS#11 module

1. Go to the server_root/alias directory containing the databases.

2. Add server_root/bin/https/admin/bin to your PATH.

3. Locate the pk12util in the server_root/bin/https/admin/bin.

4. Set the environment. For example:

   • On UNIX, use the setenv command

     LD_LIBRARY_PATH/server_root/bin/https/lib:${LD_LIBRARY_PATH}

     • On IBM-AIX, use the LIBPATH command

     • On HP-UX, use the SHLIB_PATH command

     • On Windows, add it to the PATH

       LD_LIBRARY_PATH server_root/bin/https/bin

       The PATH for your machine is listed under the server_root/https-admin/start.

5. Enter pk12util command.

   The options are listed.

6. Perform required actions.

   For example, in UNIX enter:

   pk12util -i pk12_sunspot [-d certdir][-h “nCipher”][-P https-jones.redplanet.com-jones-]

   -P must follow the -h option and be the last argument.

   Enter the exact token name including capital letters and spaces between quotation marks.

7. Enter the database password.

8. Enter the pkcs12 command password. Starting the Server with an External Certificate

   If you install a certificate into an external PKCS#11 module (for example, a hardware accelerator), the server is unable to start using the certificate until you edit the server.xml file, or specify the certificate name.

   The server always tries to start with the “Server-Cert” certificate. Certificates in external PKCS#11 modules contains one of the module’s token names in their identifier. For example, a server certificate installed on an external smartcard reader called “smartcard0” would be named “smartcard0:Server-Cert.”

   To start a server with a certificate installed in an external module, you need to specify the certificate name for the listen socket it runs on.