Why would you care that an out-of-support version (HP-NSS excepted) supports 2048 bit certificates? And what makes you think the bit-ness would be an issue rather than the algorithms it may not support? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Have you considered the time frames in which MQ v5.3 SSL support was written and maintained?
Have you examined the history of cipher changes and strengths and bitness since that time?
If you are using v5.3 in production, you should find another job. Or convince your team or client that they are criminally negligent in their systems management strategies.
I have upgraded SSL cert from 1024 bit to 2048 bit. (MQ v5.3) I have placed the certs and bounced the queue manager. And I received following error
AMQ9654: An invalid SSL certificate was received from the remote system.
EXPLANATION:
An SSL certificate received from the remote system was not corrupt but failed validation checks on something other than its ASN fields and date. The channel is 'MQM.MQM'; in some cases its name cannot be determined and so is shown as '????'. The channel did not start.
ACTION:
Ensure that the remote system has a valid SSL certificate. Restart the channel.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum