Manage your private and public key

Storing your public key within our solution store will help later on to authenticate your things-client based solutions.

things solution - public key

For setting a public key, our procedure assumes that you have generated yourself a pair of public and private key. The data of the public key file (in PKCS#8 format or a X.509 certificate) will need to be Base64 encoded.

EC stands for the EC-DSA algorithm and is the only key type supported.

The following steps use the Java keytool to do this (see Java keytool does not need to be downloaded explicitly as it is part of an average JDK. Find the official documentation at

Use this command to generate your key pair

keytool -genkeypair -noprompt -dname "CN=-, OU=-, O=-, L=-, S=-, C=-" -keyalg EC -alias things -sigalg SHA512withECDSA -validity 365 -keystore C:\temp\things-client.jks

Provide a password of your choice and confirm it. Optionally you can provide a separate second password for the key itself.

Use the following two commands to get a text representation of a certificate containing your public key.

keytool -export -keystore C:\temp\things-client.jks -alias things -rfc -file C:\temp\things-client_key.cer


keytool -printcert -rfc -file C:\temp\things-client_key.cer

create public key

Copy the text representation including —–BEGIN CERTIFICATE—– down to —–END CERTIFICATE—– into the clipboard for the public key of your solution and click “Submit public key”.
A success message should appear.

submit solution public key

If you refresh the page, the success message for submitting the key will disappear, but the key will remain stored until you overwrite it with a new one.

Keep the keystore with your private key as well as the passwords safe.
You will need them later, when using our Things Client for Java.