java -jar kmsclient.jar https://<host:encport> <did> <username> <password> LKC <AES|TDES> <128|192|256> <hex-key-component> [kcv] <K-Value> <N-Value> <key-name>
|
Value |
Explanation |
|---|---|
|
host:encport |
The URL of the KA where the CCS web service operations will be submitted.
Example: https://kms.strongauth.com:8181 |
|
did |
Unique domain identifier that belongs to SAKA The URL of the KA where the CCS web service operations will be submitted. For example, the URL can be https://kms.strongkey.com. |
|
username |
The username in the encryption domain with authorization to call the web service. |
|
password |
The password of the username above. |
|
AES|TDES |
Either the AES or Triple DES algorithm. |
|
128|192|256 |
Available key sizes accepted by the appliance. |
|
hex-key-component |
A key component value submitted as a hex-encoded string. |
|
kcv |
The Key Value Check of the key being loaded. |
|
K-Value |
The numerical identifier for a key component in a set of key components. |
|
N-Value |
The total number of key components in a set of key components. |
|
key-name |
A string identifying multiple key components as belonging to the same set. The value can be any 64-character long string (without spaces and special characters). It is merely used to identify the key components during a “Load BDK” operation. |
$ example:~/topaz> java -jar kmsclient.jar https://saka.strongkey.com:8181 1 encryptdecrypt Abcd1234! LKC AES 128 35221B86689FF3BFBDB2D9C539157B9D 781927 1 3 TestBDK
NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.reflect=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.management/javax.management.openmbean=ALL-UNNAMED --add-opens java.management/javax.management=ALL-UNNAMED --add-opens java.base/sun.security.provider=ALL-UNNAMED
Calling Load Key Component at https://saka.strongkey.com:8181...
{"DID":"1","SRID":"1788534144676","KeyName":"TestBDK","K":1,"N":3,"KCV":"781927"}