| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| OCP - openshift cloud platform |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Wed Sep 20, 2023 3:37 am Post subject: OCP - openshift cloud platform |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
We have some applications moving to OCP.
They have a SSL certificate which should be OK for MQ client to pass (using MQ JMS) to our QM (v9.2 on z/OS).
However they have it stored in some wierd (to me) OCP format.
I have told them it needs to be in a JKS like a regular JMS client, with the ibmwebspheremq<userid> label and so on,.
Anyone with experience of using MQ JMS under OCP?
They have the all client JAR files at version 9.3.2
They are getting MQRC 2393 at the moment (no surprise there!).
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
 |
| hughson |
| Posted: Fri Sep 22, 2023 2:58 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand
|
Can you share an example of what it looks like - i.e. what makes it weird?
Is there a particular file extension for example?
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Sep 22, 2023 10:48 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
OCP has its own certificate store
https://docs.openshift.com/container-platform/3.11/install_config/certificate_customization.html
They have now created a JKS - it's quite annoying that MQ client needs the client certficate label name in a certain format (even when there is only one there).
OCP uses Openjdk as the JRE, which in theory works with MQ, but they are getting MQRC 2400.
So making some progress - watch this space.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| hughson |
| Posted: Sun Sep 24, 2023 1:14 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand
|
| zpat wrote: |
| They have now created a JKS - it's quite annoying that MQ client needs the client certficate label name in a certain format (even when there is only one there). |
The MQ client has not REQUIRED a certain format name since V8. You can label your certificate anything you want and just provide the label name along with the key repository name.
That said, Java clients (I assume since JKS) don't use labels at all.
So I am a little unclear what exactly you are struggling with, perhaps if you give some more specifics we can help further?
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| 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
|
|
|
|
