| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SET AUTHREC - using AUTHRMV(ALL) then AUTHADD |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Tue Oct 14, 2014 4:59 pm Post subject: SET AUTHREC - using AUTHRMV(ALL) then AUTHADD |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.ref.adm.doc/q086620_.htm
| Quote: |
Usage notes
The list of authorizations to add and the list of authorizations to remove must not overlap. For example, you cannot add display authority and remove display authority with the same command. This rule applies even if the authorities are expressed using different options. For example, the following command fails because DSP authority overlaps with ALLADM authority:
| Code: |
| SET AUTHREC PROFILE(*) OBJTYPE(QUEUE) PRINCIPAL(PRINC01) AUTHADD(DSP) AUTHRMV(ALLADM) |
|
OK, that's straightforward.
But I intended to replicate what I did in my setmqaut scripts where, being a T.Rob disciple, I clearly remove any and all authorities before applying what I intend, knowing that I end up with only exactly what this command says and no other leftover junk.
So I try the following command, and it works:
| Code: |
| SET AUTHREC GROUP('mygroup') OBJTYPE(QMGR) AUTHRMV(ALL) AUTHADD(CONNECT) |
And that conflicts with the Knowledge Center article, since ALL clearly overlaps CONNECT.
So is the Knowledge Center Article wrong? Or am I taking advantage of a loophole that might get fixed who knows when?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| hughson |
| Posted: Wed Oct 15, 2014 3:28 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
We did consider this when we implemented the feature. In fact I raised your exact question when we were reviewing the DCR.
This resulted in the code being 'fixed' to special case AUTHADD(ALL) or AUTHRMV(ALL) to do what you would expect. However, it did not result in the docs being updated to admit to this fact.
So, you are using something that is there by design.
You cannot use both AUTHADD(ALL) and AUTHRMV(ALL) together.
If you use one or other of them it is processed first before the rest of the values.
i.e. If AUTHADD(ALL), we will first add ALL and then remove the rest
or: If AUTHRMV(ALL), we will first remove ALL and then add the rest
I will raise a doc defect internally to get this behaviour reflected in Knowledge Center.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Oct 15, 2014 4:20 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Thanks Morag!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
