| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| rfhutilc and SSL |
« View previous topic :: View next topic » |
| Author |
Message
|
| crossland |
 Posted: Mon Nov 03, 2008 3:30 am Post subject: rfhutilc and SSL |
 |
|
Master
Joined: 26 Jun 2001
Posts: 248
|
To test a SVRCONN SSL channel, I am using rfhutilc.
A bat file is used to invoke rfhutilc.
The bat file contains the following:
SET MQSERVER=<SVRCONN channel>/TCP/<ip address>(<ip port>)
rfhutilc
As per the ih03 documentation, I am setting the SSL parameters using the "Set ConnID" button as follows:
Certificate Store location - browse to key database
tick by SSL
Specify SSL cipher algorithm to be the same as on the queue manager.
Whenever I set SSLCIPH for the channel on the queue manager, the following error is produced:
AMQ9639: Remote channel '<name>' did not specify a CipherSpec.
If SSLCIPH is not set on the queue manager, rfhutilc is able to connect to the SVRCONN channel.
Is there something else that needs to be done to get rfhutilc to connect to a SSL secured SVRCONN channel? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Nov 03, 2008 3:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| AMQ9639: Remote channel '<name>' did not specify a CipherSpec. |
Explain why this would not be relevant... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| crossland |
| Posted: Mon Nov 03, 2008 3:47 am Post subject: |
|
|
Master
Joined: 26 Jun 2001
Posts: 248
|
Funnily enough, fjb, I came to the same obvious conclusion as you.
And guess what? We were both totally wrong.
When the error message states that the "Remote channel did not specify a CipherSpec", we both concluded that, well, the remote channel did not specify a cipherspec. Especially as the recommended response to this error message, in the Messages manual is to "Change the remote channel to specify a CipherSpec so that both ends of the channel have matching CipherSpecs."
And the actual cause of the problem? A typo in the certificate label. Maybe a future release will report this as a problem with the certificate label??? |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
