Using the EKM Client During the Development

This topic addresses software developers that want to perform full integration with the Dyadic solution in their development environment. It walks you through the steps to establish in-house setup that mimics integration with the Dyadic “Tile” in Pivotal Cloud Foundry (PCF). In addition, it provides you with a set of CLI commands for debugging and troubleshooting.

However, if you are mainly interested in the samples of application code, skip this topic and continue to the Code Samples.

If you have not already done so, please request the Dyadic Evaluation Package by completing this short form:


To utilize Dyadic Solution provided by PCF, your application must use Java JCE framework as the interface to the crypto operations. Dyadic plugs into the JCE framework by means of the EKM Client. The client cooperates with the cluster of EKM Servers that are already deployed . Collaboration between the Client and Servers implements the required crypto-action using Multi-Party Computation (MPC).

As the developer, you will make standard installation of one software module (EKM Client), follow Java instructions to add custom Security Provider to Java Framework, and you are all set to go.

 Dyadic EKM IDE

Note: EKM Servers are already deployed in the cloud waiting for the engagement with your application via the EKM Client.

Abbreviation Meaning Description
DSM Distributed Security Module Previous acronym of the Dyadic Solution
EKM Enterprise Key Management Production Name of the Dyadic Solution
FQDN Fully Qualified Domain Name It is a domain name that specifies its exact location in the DNS
JCE Java Cryptography Extension Java framework for implementation of crypto primitives
MPC Multi-Party Computation Crypto Technology used by Dyadic


Your development station must run one of the following OSs:

Operating System Version
Windows 7, 8.1, 10 (32) and (64)
2008 R2 (64)
2012 R2 (64)
Linux RHEL 6.5 (32) and (64) and up
CentOS 6.5 (64) and up
Ubuntu 12.04 (64) and up
  1. Your Application must use JCE Framework for the realization of crypto operations

  2. If your development station is Linux - libapr version 1.3 or newer must be installed

    To install it on Red Hat use

    sudo yum install apr

  3. Your Firewall should allow connection to EKM Server over TCP Port 61615

Installing and Starting EKM Client on your Development Station

Unboxing the Package

The Package you obtained from Dyadic includes Software and Data files.

The Software section contains OS-specific EKM Client SW:

OS Name of File
RHEL dsm-client-{version}-RHES.x86_64.rpm
UBUNTU dsm_client.{version}.DEBIAN_amd64.deb
Windows dsm_client_{version}_Windows.x64.msi

The Data section contains the Address of the EKM Server and Certificate files required to establish SSL connection with it (via TCP port 61615)

Item Description
EKM Server Address Address of the EKM Server in the FQDN format.
For example:
key.pem SSL Authentication Certificate. It contains the Private Key
ca.crt Root Certificate of EKM

Installing the EKM Client

Use the following table to install EKM Client SW (called “dsm client”) that matches the OS of your development station:

OS Command
sudo yum localinstall dsm-client-{version}-RHES.x86_64.rpm 
sudo dpkg -i dsm_client.{version}.DEBIAN_amd64.deb 

  1. Plug Dyadic dsm-advapi jar file into JCE by copying or soft-linking it into <Java Directory>/jre/lib/ext. For example:

    OS Command
    sudo ln -s /usr/lib64/dsm/dsm-advapi-1.0.jar    /usr/lib/jvm/java-8-openjdk-amd64/jre/lib64/ext/
    sudo ln -s /usr/lib/dsm/dsm-advapi-1.0.jar    /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext/
    cp C:\dsm\dsm-advapi-1.0.jar    C:\Program Files (x86)\Java\jre1.8.0_111\lib\ext 
  2. Edit the file, and insert the reference to Dyadic as one of the crypto providers (DYCryptoProvider):

    OS An Example of Folder containing the file
    RHEL /usr/lib/jvm/java-8-openjdk-amd64/jre/lib64/security
    UBUNTU /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/security
    Windows C:\Program Files (x86)\Java\jre1.8.0_111\lib\security

We recommend to insert Dyadic (security.provider.5=com.dyadicsec.provider.DYCryptoProvider) before the reference to the SunJCE as shown below
    security.provider.5=com.dyadicsec.provider.DYCryptoProvider  // insert DYADIC here

Note You must renumber all entries in the list starting with the newly inserted Provider.

Configuring the EKM Client

The configuration of the EKM Client is straightforward. It requires you to specify the Network Name of the EKM Server (EKM Server Address) as received with the package.

OS Folder
Linux Open client.conf file in the /etc/dsm folder
Windows Navigate to the registry key: HKEY_LOCAL_MACHINE/SOFTWARE/DyadicSec/SDK

Set servers=<EKM Server Address>. For example:

servers =

Activating EKM Client-Server Connection

To Activate connection between EKM Client and its Server, place the received Access Credentials ( key.pem and ca.crt ) files in the following folder:

OS Folder
Linux /etc/dsm
Windows C:\ProgramData\dyadic\dsm

Note By default, the ProgramData directory in Windows is hidden. Create the dyadic and dsm folders, as needed.

To verify the connection, run dsmcl list command.

$ dsmcl list

Partition 0: test
Private RSA key  : UID=b9d3a8dddd7e379a
Private RSA key  : UID=e81a67a6d10348ac

Troubleshooting the Installation

Problem What happened What to do about it
Unable to install EKM You may be using an unsupported OS or (on Linux) “apr” is missing Make sure: are using one of the supported OSs.
2. (on Linux) apr is missing
Unable to activate Client-Server connection The address of the Server is mistaken or the connection is blocked Verify the following:
1. /etc/dsm/client.conf or appropriate Windows Register specifies the correct EKM Server.
2. Connection to the Server over TCP port 61615 is not blocked

Appendix A: CLI For EKM Observer

This sub-topic provides additional information to assist you while testing and debugging your application.

Installation of the EKM Client added dsmcl CLI program on your development station. Use it to examine and manipulate EKM crypto objects created on your behalf by EKM Client and Servers. The overall syntax is:

dsmcl [command] [options]

dsmcl list

Use the list command to view crypto objects (e.g., keys, certificates) and their attributes such as Unique ID (UID), name, description.

  • UID is used as the parameter in the Object-specific CLIs
  • name is used in Dyadic APIs.
  • description is a free text.

Syntax: dsmcl list [-t <object type>]

Option Description
-t <type> Filters the list of objects by the type:
dsmcl list
dsmcl list -t RSA
dsmcl list -t CERT

dsmcl show

Use the show command to see the contents of the selected object(s). You can specify the UID of the object or the type. The latter options presents all objects of the specified type

Syntax: dsmcl show [(-u <uid> | -t <type>)]

Option Description
-u <UID> The UID of a crypto-object. Obtain it using the list command
-t <type> The type of the objects to be shown
dsmcl show -u e9b653de39be17bd
dsmcl show -t RSA

dsmcl change-info

Use this command to set or modify the name or description of the object.

Syntax: dsmcl change-info -u <UID> ([-n <name>] | [-d <description>])

Option Description
-u <UID> The Unique Identification Number of an object, such as a key
A mandatory parameter
-n <name> The new name of the object
-d <description> The new description of the object
dsmcl change-info -u 055e36fe83358cd4 -n apache -d "description with spaces"

Appendix B: Creating/Deleting and Exporting/Importing EKM Objects

This set of CLI commands takes you one level deeper into EKM. It allows you manually create and manipulate EKM Objects, and import or export keys and certificates.

dsmcl generate

Use to generate a new key of the required type and the proper attributes

Syntax: dsmcl generate -t <type> -s <size> [-n <name> -d <description>] -c <curve> -m (S|E|D)

Option Used with Description
-t Type of the key: - mandatory parameter. One of the following:
-s -t RSA -t AES Key size, when the key is RSA or AES: 128,256,2048,3072,4096
-n Name of the new key
-d Description of the new key
-c -t ECC EC curve to use, when the key is EC key: P256,P384,P521
-m -t ECC Used with ECC. Mandatory parameter. Specifies the purpose of the Key:
S for Sign, E for dEcrypt, or D for Derive
dsmcl generate -t (RSA | AES) -s (128 | 256 | 2048 | 3072 | 4096)
dsmcl generate -t ECC -c (P256 | P384 | P521) -m (S,E,D)

dsmcl delete

Syntax: dsmcl delete -u <UID>

Option Description
-u The UID of the object to be deleted
dsmcl delete -u 0x6AA15948

Note Deleting of an object is final - it cannot be recovered. In particular, data that was encrypted with the deleted key cannot be decrypted.

dsmcl export

This command supports integration with other systems by providing a public key which can be used to encrypt data or verify a signature. You can export the following objects:

  • Certificate - File in CER format

  • Public Key – File in PEM format

Syntax: dsmcl export -u <UID> -o <output-file-name> [-x]

Option Description
-u (UID) The UID of the selected object
-o File to store the data
-x This option obfuscates the data.
It is done just for the sake of compatibility with the OpenSSL
dsmcl export -u 629d6e5c500c6b04 -o c:\test\key1.pem

dsmcl import

You can import an RSA or ECC key/certificate into EKM Client. The supported file formats are PEM, CER, and PKCS#12 file formats.

Syntax: dsmcl import -i <filename> [-p <password>] [-f <format>] [-n <name>] [-d <description>] -k -ca -m S [-x]

Option Description
-i (file) The input file
-p (password) The PFX/P12 password
-f The format of the import file: PEM,CER,P12
-n (name ) The name of the imported key
-d (description) The description of the new key
-k Don’t import the certificate, if such exists, import only the private key
-ca If the file contains a key certificates chain, import all certificates in the chain to EKM as well.
-l add a label to the key you are importing
-m (S,E,D) for ECC file formats, specify the purpose: S for Sign, E for dEcrypt, and D for Derive
-x Override the original file, replace private key material with obfuscated data
dsmcl import -i 2048.pfx -p 123456

Appendix C: Configurable Attributes of the EKM Client

This sub-topic provides additional information to assist you while testing and debugging your application.

We already met the requirement to specify the EKM Server that serves the Client. The rest of the attributes are defaults, and, by convention, the absence of the specific name-value pair implies that the default value is being used. Though it is highly unlikely that you will have to change the default values, the following is provided for your information, just in case:

  • On Linux: edit the client.conf file

  • on Windows by adding registry keys to HKEY_LOCAL_MACHINE/SOFTWARE/DyadicSec/SDK.

Setting Description Default
servers String. The list of EKM EPs serving the client N/A
ha_mode_standby Boolean. If set to true, the client will always connect to the first server in the list and will fall back to the next server in the list only if the first server fails and so on. When set to false, the client will arbitrarily pick a server to connect to and move to a different server on failures. false
send_timeout Milliseconds. The timeout to wait on sending a request to the current EKM EP. If the timeout expires and all retries are consumed, the client will try to connect to a different server according to ha_mode_standby specification. 10 seconds
recv_timeout Milliseconds. The timeout to wait for a response from the EKM EP server after the message was sent. If the timeout expires and all retries are consumed, the client will try to connect to a different server according to ha_mode_standby specification. 20 seconds
retries Integer. Indicates the total number of attempts the client makes to contact with the EKM Server 2
Was this helpful?
What can we do to improve?
Create a pull request or raise an issue on the source for this page in GitHub