Troubleshooting
Problem
By default, some of the WebSphere MQ SSL certificate management tools used the MD5 digital signature algorithm when generating certificates and certificate requests. Many users no longer regard MD5 as sufficiently secure and choose to use an alternative algorithm. This technote explains how to do so.
Symptom
When using iKeycmd (gsk7cmd and runmqckm) tools or the iKeyman GUI equivalents (gsk7ikm and strmqikm) to create self-signed certificates or certificate signing requests, you notice that the MD5 digital signature algorithm has been used.
[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Component":"SSL","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0.1;7.0.0.2;7.0.0.1;7.0;6.0.2.7;6.0.2.6;6.0.2.5;6.0.2.4;6.0.2.3;6.0.2.2;6.0.2.11;6.0.2.10;6.0.2.1;6.0.2;6.0.1.1;6.0.1;6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
28 April 2025
UID
swg21390394