|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
OAM anomaly |
« View previous topic :: View next topic » |
Author |
Message
|
ivanachukapawn |
Posted: Wed Apr 01, 2015 1:28 pm Post subject: OAM anomaly |
|
|
 Knight
Joined: 27 Oct 2003 Posts: 561
|
Running a MQ8.0.0.2 qmgr, I have effectively disabled connection authentication (by specifying none for client and local connections in IDPWOS). I kept the default CHLAUTH rules (blocking *MQADMIN, SYSTEM.* and allowing MQ Explorer channel access). I don't have a backstop rule yet. Using the ID of a non-privileged user, I attempted to dmpmqmsg connect to the QM and copy a message from TEST.QUEUE1 to TEST.QUEUE2. But I get error message: "MQOPEN on object 'TEST.QUEUE2' returned 2035 Not authorized" - as both CHLAUTH and connection authentication seem irrelevant to this behavior, I have assumed OAM as the error message source. But I have setmqaut for this QM/user as follows Profile: TEST.QUEUE2 object type: queue Entity: user1 Entity Type: group (this is odd. I specifying -p on my setmqaut command) authority: get browse put inq and the same for TEST.QUEUE1 - to permit the QMGR connection, I setmqaut to yield profile: self object type: qmgr entity: user1 entity type: group Authority: inq connect dsp - don't know why I'm getting this error. I enabled authority events and got some messages but their text is not helpful. And incidentally, I refreshed the authorization service after running the setmqauts. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Apr 01, 2015 8:20 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
What's the difference in the dmpmqaut for TEST.QUEUE1 and for TEST.QUEUE2?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
ivanachukapawn |
Posted: Thu Apr 02, 2015 7:18 am Post subject: |
|
|
 Knight
Joined: 27 Oct 2003 Posts: 561
|
the run of dmpmqmsg is supposed to copy a message from TEST.QUEUE1 to TEST.QUEUE2 - I ran dmpmqmsg just once - and surprised to see the 2035 related to TEST.QUEUE2 - kinda implies that dmpmqmsg could connect to the QMGR - and maybe didn't have a problem with TEST.QUEUE1 and gets a 2035 on TEST.QUEUE2 - but my setmqaut for this user on TEST.QUEUE2 specifies +PUT (this is the specified -o output queue. |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Apr 02, 2015 8:30 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
ivanachukapawn wrote: |
the run of dmpmqmsg is supposed to copy a message from TEST.QUEUE1 to TEST.QUEUE2 - I ran dmpmqmsg just once - and surprised to see the 2035 related to TEST.QUEUE2 - kinda implies that dmpmqmsg could connect to the QMGR - and maybe didn't have a problem with TEST.QUEUE1 and gets a 2035 on TEST.QUEUE2 - but my setmqaut for this user on TEST.QUEUE2 specifies +PUT (this is the specified -o output queue. |
+ put may not be enough. Have you considered that you might need +setall ?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
ivanachukapawn |
Posted: Thu Apr 02, 2015 10:05 am Post subject: |
|
|
 Knight
Joined: 27 Oct 2003 Posts: 561
|
Thanks FJB,
I hadn't considered it but I added it in on setmqaut for the qmgr and the 2 queues. Now it works. |
|
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
|
|
|
|