Authentication on MQ server through SoapUI
Hi
I'm using SoapUI Pro and am trying to put messages on our MQ server (an IBM WebSphereMQ) through SoapUI via Hermes JMS, however when I try I get a JMS exception as follows:
I used to have a similar problem with Hermes JMS which was resolved by sending empty credentials through the default channel (i.e you check "User" under "Preferences => Sessions => Connection" in Hermes JMS but leave the fields blank) but now it seems I'm stuck again. I don't have access to the MQ server so modifications on the server side is not an option and while I try to cut through the red tape I'm trying to find a temporary solution to this.
So, is it possible to send empty credentials, that is empty username/password, the same way you can do in Hermes JMS, either by some configuration or header tag? Or is there any other viable solution to this problem?
I'm using SoapUI Pro and am trying to put messages on our MQ server (an IBM WebSphereMQ) through SoapUI via Hermes JMS, however when I try I get a JMS exception as follows:
javax.jms.JMSException: MQJMS2013: invalid security authentication supplied for MQQueueManager
at com.eviware.soapui.impl.wsdl.submit.transports.jms.JMSConnectionHolder.<init>(JMSConnectionHolder.java:77)
at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestSendTransport.execute(HermesJmsRequestSendTransport.java:34)
at com.eviware.soapui.impl.wsdl.submit.transports.jms.HermesJmsRequestTransport.sendRequest(HermesJmsRequestTransport.java:84)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I used to have a similar problem with Hermes JMS which was resolved by sending empty credentials through the default channel (i.e you check "User" under "Preferences => Sessions => Connection" in Hermes JMS but leave the fields blank) but now it seems I'm stuck again. I don't have access to the MQ server so modifications on the server side is not an option and while I try to cut through the red tape I'm trying to find a temporary solution to this.
So, is it possible to send empty credentials, that is empty username/password, the same way you can do in Hermes JMS, either by some configuration or header tag? Or is there any other viable solution to this problem?