| Author |
Message
|
| eugene |
 Posted: Thu Jun 03, 2010 12:20 am Post subject: User not able to connect to Queue Manager |
 |
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
It has been only a few days after my last question here and it seems that I have run (again) into a problem that I have no idea how to deal with. 
We have 2 users on the OS where QM is installed, both part of the mqm group - let's call them user1 and user2.
We have created a new user (user3) that is made part of the mqm group. With this user we can perform stuff like mqsilist, mqsistop, strmqm, etc (ssh connected). But from a remote computer when trying to connect to QM with WMQTool or RHFUtil it says "Not authorized". Isn't it the mqm group able to connect to queue manager, not the single user? Also we have tried to stop/start queue manager - it did not work. The logs at /var/mqm/qmgrs/MDWMBQM/errors are clean - not a single entry today.
Any hints?
Thank you,
Eugene. |
|
| Back to top |
|
 |
| eugene |
| Posted: Thu Jun 03, 2010 12:22 am Post subject: |
|
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
"Also we have tried to stop/start queue manager - it works fine".. Sorry  my bad for the typo. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Thu Jun 03, 2010 1:03 am Post subject: Re: User not able to connect to Queue Manager |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| eugene wrote: |
| But from a remote computer when trying to connect to QM with WMQTool or RHFUtil it says "Not authorized". |
What's the value of MCAUSER in the channel definition?
| eugene wrote: |
| We have 2 users on the OS where QM is installed, both part of the mqm group - let's call them user1 and user2. |
You shouldn't really be putting your users in mqm group. Use the setmqaut command to give them access to only those objects they need access to.
Amen.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| eugene |
| Posted: Thu Jun 03, 2010 1:48 am Post subject: |
|
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
MAUSER is set to default, it is ''.
Well yes thought about that too - but the interesting part is that I have run dsmqaut for that user (user3) and it has the "connect" privileges |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Jun 03, 2010 2:20 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Sorry, I couldn't figure this out... where is 'user3' defined in this case - is it on the qmgr machine or the remote machine? If it's on the qmgr machine, what are the credentials of the user connecting in remotely? |
|
| Back to top |
|
|
| eugene |
| Posted: Thu Jun 03, 2010 2:40 am Post subject: |
|
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
User3 is defined on the qmgr machine.
Hmmm.. why is there the need of the credentials of the user who is connecting remotely? Anyway the remote machine is a Windows box that has the "user3" defined and WMQTool and RHFUtil are run from that particular user. The same machine has "user2" and "user1" defined and they both can connect to the qmgr.
Big big thx for helping out here... |
|
| Back to top |
|
|
| eugene |
| Posted: Thu Jun 03, 2010 3:12 am Post subject: |
|
|
Novice
Joined: 02 Mar 2010
Posts: 18
|
Well it finally was solved! 
But it seems to me that a PMR has to raised. What we did is get the trace going on the qmgr. Out user's name is actually "USER", but in logs we could see that it was "user". We deleted the "USER" and added "user" - gave him all the rights and it worked. It seems to me that this is queue manager issues from some C/C++ library, but not sure where is comes from. Will try to reproduce this on some Linux/Windows boxes.
Thx a lot for everyone's help and time spent! |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jun 03, 2010 4:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| eugene wrote: |
Will try to reproduce this on some Linux/Windows boxes.
|
I think you'll reproduce this behaviour quite easily. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
