| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WMB7 unauthorized user stop flow command gets stuck |
« View previous topic :: View next topic » |
| Author |
Message
|
| hopsala |
 Posted: Sun Sep 25, 2011 7:06 am Post subject: WMB7 unauthorized user stop flow command gets stuck |
 |
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Hey, I've got an odd one for ya:
I have a channel with an MCAUSER('user1') authorized to view an EG but not authorized to control it. When I try to stop a message flow the toolkit gets stuck on the "stopping message flow xxx..." window, until I restart the toolkit.
Unless I'm missing something, I should be getting some sort of "not authorized" message instead of getting stuck. When I try to deploy, for example, I do get a BIP2852E "user not authorized message". Other authorized users can issue commands without a hitch, and I get the same result from another workspace and from another machine with a toolkit.
Has anyone tried this and gotten a different result? Has anyone come across this behavior?
The environment is WMB 7.0.0.2, toolkit 7.0.0.2 and WMQ 7.1.0.5.
The list of authorizations is as follows:
setmqaut -m QM1 -t qmgr -g group1 +connect +dsp +inq
setmqaut -m QM1 -n SYSTEM.MQEXPLORER.REPLY.MODEL -t queue -g group1 +browse +get +inq +dsp
setmqaut -m QM1 -n SYSTEM.ADMIN.COMMAND.QUEUE -t queue -g group1 +dsp +browse +put
setmqaut -m QM1 -n SYSTEM.BROKER.DEPLOY.QUEUE -t queue -g group1 -all +put
setmqaut -m QM1 -n SYSTEM.BROKER.DEPLOY.REPLY -t queue -g group1 -all +put +get
setmqaut -m QM1 -n SYSTEM.BROKER.AUTH -t queue -g group1 -all +inq
setmqaut -m QM1 -n SYSTEM.BROKER.AUTH.** -t queue -g group1 -all +inq
Thanks!
H
 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Sep 25, 2011 7:13 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You're sure you don't need to add browse to the broker authorization queue? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| hopsala |
| Posted: Sun Sep 25, 2011 8:03 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Sep 25, 2011 12:42 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Sep 26, 2011 2:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I think you're missing the point of the question?
The question does not appear to be what permissions are needed to control a broker.
The question appears to be "why does the toolkit hang under a certain set of permissions".
hopsala - please try applying maintenance to toolkit and then look at the workspace log file for anything that might resemble a clue. |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Sep 27, 2011 1:24 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Jeff is basically right, my question was about why the toolkit gets stuck, not how to set up authorities. In a way, the authority settings I placed are working - the user can't stop the flow.
But while we're at it, discussing how to set up authority doesn't hurt. Saper - in the link you gave me it only says to give +set authorities for developers, that is, for someone who needs to deploy, but what I'm looking for is view-only permission. The links I posted earlier say that broker 'read' authority means +inq in mq, and that to view the broker all you need is +inq on AUTH queue.
I'm not sure what +set means on the AUTH queue level. Since permissions are not inherited to specific EGs, this should have something to do with the broker level. Maybe change or view broker properties?
Anyway, I wasn't aware that maintenance 7.0.0.3 came out a month ago. I'm downloading it now. Will keep you posted. |
|
| 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
|
|
|
|
