|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ Authorization - 2035 Error |
« View previous topic :: View next topic » |
Author |
Message
|
skycoolers |
Posted: Thu Dec 22, 2005 9:03 am Post subject: MQ Authorization - 2035 Error |
|
|
 Apprentice
Joined: 22 Dec 2005 Posts: 35
|
Hi,
I am new to MQ, using MQSERVER 5.3 Windows version. I am getting 2035 error (Authorization) when I publish message from MQClient 5.3(Solaris).
I want to suppress the authorization in MQSERVER. i.e. Irrespective of the USERID, MQSERVER should accept all the messages. Please let me know what command I should use.
Regards,
Siva |
|
Back to top |
|
 |
csmith28 |
Posted: Thu Dec 22, 2005 10:06 am Post subject: |
|
|
 Grand Master
Joined: 15 Jul 2003 Posts: 1196 Location: Arizona
|
The Client will be accessing the MQManager with a UserID. That ID must exist on the local server and either be in the MUSR_MQADMIN group or that UserID must be granted the appropriate authority to access the MQManager and Objects using the setmqaut command.
You may have to set the value of MCAUSER to the UserID of the Client application.
An alternative is to set the MCAUSER value to MUSR_MQADMIN but this is not wise.. _________________ Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
Back to top |
|
 |
skycoolers |
Posted: Thu Jan 05, 2006 10:39 am Post subject: |
|
|
 Apprentice
Joined: 22 Dec 2005 Posts: 35
|
Hi Smith,
Thanks for your response.
I tried setting the value of MCAUSER to the UserID of the Client application, but it is not working.
Your alternative solution is working fine, i.e. setting the MCAUSER value to MUSR_MQADMIN. Can you please tell me why this approach is not wise.
Regards,
Siva |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Jan 05, 2006 10:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
When the MCAUSER is set to MUSR_MQADMIN, then *anyone* who connects to that channel is now fully priviledged to do anything on the qmgr.
Anything at all.
Setting the MCAUSER without doing the other things mentioned - ensure that the ID exists on the local server AND has privileges either by being in MUSER_MQADMIN or by using setmqaut will, as you have experimentally proven, do nothing. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
skycoolers |
Posted: Thu Jan 05, 2006 11:27 am Post subject: |
|
|
 Apprentice
Joined: 22 Dec 2005 Posts: 35
|
Thanks for responding immediately.
Your's and csmith's solution worked out, thank you |
|
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
|
|
|
|