try using curl command and verify. Postman might not show the name correctly.
Original Message:
Sent: Fri July 14, 2023 02:32 AM
From: Sebastian Wilk
Subject: REST Messaging with Postman or Curl AND SSL Certificates
The Clientcert is based on the User AP44W, but for whatever reason, Postman shows it as localhost, and I have no idea why nor does any documentation point towards that problem.
The truststore of the webserver hosts the public part of the certifcate as well.
------------------------------
Sebastian Wilk
Original Message:
Sent: Wed July 12, 2023 11:04 AM
From: om prakash
Subject: REST Messaging with Postman or Curl AND SSL Certificates
the client cert CN should be a valid user which IBM MQ will validate. If it is not; it will fail.
Also, the Cert should be part of the webserver store.
------------------------------
om prakash
Original Message:
Sent: Thu July 06, 2023 02:53 AM
From: Sebastian Wilk
Subject: REST Messaging with Postman or Curl AND SSL Certificates
Hello once again dear mq people,
I have been exploring the REST API for MQ and playing around with it for a while and been struggling to set up a connection with SSL using certificates.
The following setup is being used:
Queuemanager version 9.3.0.5 on a Windowsmachine.
Either Postman or curl is used to Put and Get messages.
Port 9080 is enabled for HTTP and 9443 for HTTPS, as well as the security parameters in the webuser.xml according to the MQ documentation found here
Using client certificate authentication with the REST API and IBM MQ Console - IBM Documentation
It works using the following parameters:
HTTP://ip.lan-domain:9080/ibmmq/rest/v2/messaging/qmgr/MQWINW02/queue/TEST.QUEUE.LQ00/message
I can send and receive messages this way using the username and password which is defined in the webuser.xml
Trying the same call with HTTPS and a certificate instead does not work and I receive the following error:
HTTPS://ip.lan-domain:9443/ibmmq/rest/v2/messaging/qmgr/MQWINW02/queue/TEST.QUEUE.LQ00/message
MQWB0104E
The REST API request cannot be completed because credentials were omitted from the request. On z/OS, if the mqweb server has been configured for SAF authentication, this can be caused by the Liberty angel process not being active.
I have added the certificate in the options menu in postman
Checking the network part I can see this
I receive the same error message using the call in curl providing the certifcate via --cert-type and --cert parameters.
Any pointers would be greatly appreciated! Be that tutorials or debugging options.
Kind regards
Sebastian
------------------------------
Sebastian Wilk
------------------------------