lorex client 13 not able to connect after changing password

Runmqakm -certreq -create -db key.kdb -pw password -label ibmwebspheremquser -dn distinguishedname -size size -file ibmwebspheremquser -fips -sig_alg algĪdding downloaded CA signed certs to key db: Runmqakm -keydb -create -db key.kdb -stash -pw password -type cms -expire number Here are the steps I followed initially to add CA certs to key db: key db creation: How can I change key repo(test.kdb) to be as below, with clientcert identified/added as personal certificate in key db runmqakm -cert -list -db test.kdb -stashed

SSLCAUTH attribute is set to OPTIONAL and it has no SSLPEER value set.

If you haveĬonfigured a certificate label, check that the certificate exists.Īlternatively, if appropriate, change the remote channel definition so that its SSL or TLS handshaking, but a certificate is required by the remote queueĮnsure that the key repository of the local queue manager or MQ client containsĪ certificate which is associated with the queue manager or client. The channel 'xyz' did not supply a certificate to use during * default, - personal, ! trusted, # secret keyĭue to which I get below error EXPLANATION: Runmqakm -cert -list -db test.kdb -stashed When I import the new certs, client cert is getting imported as trust certificate instead of personal certificate runmqakm -cert -add -label clientcert -db test.kdb -stashed -file personalcert

Lorex client 13 not able to connect after changing password