| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Which user starts que queue manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| HenriqueS |
 Posted: Thu Dec 06, 2007 9:16 am Post subject: Which user starts que queue manager |
 |
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Hello folks...
I have noticed some unexpected behaviour that I want to share (WinXP).
When trying to force a qmgr to start under a specific user name, I tried
'contact admin /user:mymachine\anotheruser cmd' then 'amqmdain start ...'
AND
'contact admin /user:mymmachine\anotheruser cmd' then 'strmqm'
In both cases the runmqchi process (and therefore all receiver channels set their MCAUSER Id to) is initiated under MY username (actually the username that is running the desktop and is the one who installed the product).
In the beggining I thought that the runmqlsr user context would be used for the MCAUSER Ids, but it seems that the queue manager start procedure is the one that automatically starts the runmqchi, and that the runmqchi user context is the one given to the MCAUSER ids.
So, how can I force another user for the runmqchi start?
_________________
HenriqueS
Certified Websphere MQ 6.0 System Administrator |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Dec 06, 2007 10:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What are you trying to accomplish by trying to do this very strange thing?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| HenriqueS |
| Posted: Fri Dec 07, 2007 4:54 am Post subject: |
|
|
Master
Joined: 22 Sep 2006
Posts: 235
|
Actually it is for the sake of curiosity, I am going over about MCAs and the ways they are filled on runtime if left blank. I wanted just to check whether the user that runs:
a) runmqlsr
b) runmqchi
c) strmqm or amqmdain
is the one pushed as MCA user id on a receiver channel.
If I recall, the redbook says the assigned user is the one that starts the runmqchi ('channel initiator address space'). But what happens here is that the user that starts the queue manager (strmqm or amqmdain) is the one assigned to the MCAUSER property at runtime. So I guess the redbook does not clarify this right.
Oh well, this is not a killer issue...
_________________
HenriqueS
Certified Websphere MQ 6.0 System Administrator |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Dec 07, 2007 5:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You have to assume that any MQ processes will be running with full mqm permissions.
You have to assume that any channel without an MCAUSER on it will provide full administrative access to any queue manager that is reachable from the qmgr at the end of the channel.
Particularly on Windows, mq processes may not be running as the user that is being reported in Task Manager. There's some tricky stuff going on behind the covers involving DCOM and respawning processes under different authorities. The Windows equivalent of "su -c".
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
