Commands for cryptographic device operations

We can use the runmqckm (iKeycmd), and runmqakm commands to manage keys and certificates for cryptographic device operations.

Note: IBM MQ does not support SHA-3 or SHA-5 algorithms. You can use the digital signature algorithm names SHA384WithRSA and SHA512WithRSA because both algorithms are members of the SHA-2 family.

The digital signature algorithm names SHA3WithRSA and SHA5WithRSA are deprecated because they are an abbreviated form of SHA384WithRSA and SHA512WithRSA respectively.

    -keydb -changepw
    Change the password for a cryptographic device: 
    -keydb -changepw -crypto module_name -tokenlabel token_label
-pw password -new_pw new_password

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -keydb -list
    List currently-supported types of key database: 
    -keydb -list

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -add
    Add a certificate from a file to a cryptographic device: 
    -cert -add -crypto module_name -tokenlabel token_label
-pw password -label label -file filename -format 
ascii | binary

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -create
    Create a self-signed certificate on a cryptographic device: 
    -cert -create -crypto module_name -tokenlabel token_label

-pw password -label label -dn distinguished_name
-size 1024 | 512
-x509version 3 | 1 | 2 -default_cert no
| yes -expire days
-sig_alg MD2_WITH_RSA | MD2WithRSA |
MD5_WITH_RSA | MD5WithRSA |
SHA1WithDSA | SHA1WithRSA |
SHA256_WITH_RSA | SHA256WithRSA |
SHA2WithRSA | SHA384_WITH_RSA |
SHA384WithRSA | SHA512_WITH_RSA |
SHA512WithRSA | SHA_WITH_DSA |
SHA_WITH_RSA | SHAWithDSA |
SHAWithRSA
    Note: We cannot import a certificate containing multiple OU (organizational unit) attributes in the distinguished name.

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -delete
    Delete a certificate on a cryptographic device: 
    -cert -delete -crypto module_name -tokenlabel token_label
-pw password -label label

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -details
    List the detailed information for a specific certificate on a cryptographic device: 
    -cert -details -crypto module_name -tokenlabel token_label

-pw password -label label

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    List the detailed information and show the full certificate for a specific certificate on a cryptographic device: 

    -cert -details -showOID -crypto module_name -tokenlabel 
token_label
-pw password -label label

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -extract
    Extract a certificate from a key database: 
    -cert -extract -crypto module_name -tokenlabel token_label
-pw password -label label -target filename
-format ascii | binary

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -import
    Import a certificate to a cryptographic device with secondary key database support: 
    -cert -import -db filename -pw password -label label
-type cms
-crypto module_name -tokenlabel token_label -pw 
password
-secondaryDB filename -secondaryDBpw password

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -import -db filename -pw password -label label
-type cms
-crypto module_name -tokenlabel token_label -pw 
password
-secondaryDB filename -secondaryDBpw password -fips

    Import a PKCS #12 certificate to a cryptographic device with secondary key database support: 

    -cert -import -file filename -pw password -type pkcs12
-crypto module_name -tokenlabel token_label -pw 
password
-secondaryDB filename -secondaryDBpw password

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -import -file filename -pw password -type pkcs12
-crypto module_name -tokenlabel token_label -pw 
password
-secondaryDB filename -secondaryDBpw password -fips
    Note: We cannot import a certificate containing multiple OU (organizational unit) attributes in the distinguished name.

    -cert -list
    List all certificates on a cryptographic device: 
    -cert -list all | personal | CA
-crypto module_name -tokenlabel token_label -pw 
password

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -cert -receive
    Receive a certificate from a file to a cryptographic device with secondary key database support: 
    -cert -receive -file filename -crypto module_name -tokenlabel 
token_label
-pw password -default_cert yes | no
-secondaryDB filename -secondaryDBpw password -format 
ascii | binary

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    Use the runmqakm command:

    -certreq -create
    Create a certificate request on a cryptographic device: 
    -certreq -create -crypto module_name -tokenlabel token_label

-pw password -label label -dn distinguished_name
-size 1024 | 512 -file filename
-sig_alg MD2_WITH_RSA | MD2WithRSA | MD5_WITH_RSA
|
MD5WithRSA | SHA1WithDSA | SHA1WithRSA
|
SHA256_WITH_RSA | SHA256WithRSA
SHA2WithRSA | SHA384_WITH_RSA |
SHA384WithRSA | SHA512_WITH_RSA |
SHA512WithRSA | SHA_WITH_DSA |
SHA_WITH_RSA | SHAWithDSA |
SHAWithRSA
    Note: We cannot import a certificate containing multiple OU (organizational unit) attributes in the distinguished name.

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -certreq -delete
    Delete a certificate request from a cryptographic device: 
    -certreq -delete -crypto module_name -tokenlabel token_label

-pw password -label label

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -certreq -details
    List the detailed information of a specific certificate request on a cryptographic device: 
    -certreq -details -crypto module_name -tokenlabel token_label

-pw password -label label

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    List the detailed information about a certificate request and show the full certificate request on a cryptographic device: 

    -certreq -details -showOID -crypto module_name -tokenlabel 
token_label
-pw password -label label

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -certreq -extract
    Extract a certificate request from a certificate request database on a cryptographic device into a file: 
    -certreq -extract -crypto module_name -tokenlabel token_label

-pw password -label label -target filename

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

    -certreq -list
    List all certificate requests in the certificate request database on a cryptographic device: 
    -certreq -list -crypto module_name -tokenlabel token_label

-pw password

    If we are using certificates or keys stored on PKCS #11 cryptographic hardware, note that runmqckm and strmqikm are 64-bit programs. External modules required for PKCS #11 support will be loaded into a 64-bit process, therefore you must have a 64-bit PKCS #11 library installed for the administration of cryptographic hardware. The Windows and Linux x86 32-bit platforms are the only exceptions, as the strmqikm and runmqckm programs are 32-bit on those platforms.

Parent topic: runmqckm, and runmqakm commands