| Author |
Message
|
| messg_wb |
 Posted: Wed Oct 13, 2010 7:37 am Post subject: ACL Entry to control flow but not deploy |
 |
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
Hi - I have msg broker at 6.0.0.9 on AIX, I am trying to create an acl entry, through which flow can be started/stopped but msg flow/set cannot be deployed, I tried specifying "E" in -x option but doesn't work (below is command and output), Can anybody suggest me workaround
/var/mqsi=> mqsicreateaclentry configMgr -u user -a -x E -p
BIP1775S: Invalid AccessControlEntry permission 'E' for object type 'ConfigManagerProxy'.
The Configuration Manager has been asked to create an Access Contol Entry with a permission of 'E' for an object of type 'ConfigManagerProxy'. This permission is invalid for this type.
Thanks |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 13, 2010 9:10 am Post subject: Re: ACL Entry to control flow but not deploy |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| messg_wb wrote: |
Hi - I have msg broker at 6.0.0.9 on AIX, I am trying to create an acl entry, through which flow can be started/stopped but msg flow/set cannot be deployed, I tried specifying "E" in -x option but doesn't work (below is command and output), Can anybody suggest me workaround
/var/mqsi=> mqsicreateaclentry configMgr -u user -a -x E -p
BIP1775S: Invalid AccessControlEntry permission 'E' for object type 'ConfigManagerProxy'.
The Configuration Manager has been asked to create an Access Contol Entry with a permission of 'E' for an object of type 'ConfigManagerProxy'. This permission is invalid for this type.
Thanks |
You cannot apply this authorization to the configmgr. You need to specify a broker, execution group and maybe a flow name... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| messg_wb |
| Posted: Wed Oct 13, 2010 12:47 pm Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
Thanks for your reply.
I tried giving broker / exec grop aswell but no luck |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 13, 2010 4:01 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| messg_wb wrote: |
Thanks for your reply.
I tried giving broker / exec grop aswell but no luck |
Define "no luck".
The same error message?
Or a different one? |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Oct 13, 2010 11:51 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
Try generating and amending it in XML format (I find it easier as it will list out all the execution groups ready for adding ACL entries).
mqsilistaclentry <configmanager> -f file.xml |
|
| Back to top |
|
|
| messg_wb |
| Posted: Fri Oct 15, 2010 7:13 am Post subject: |
|
|
Acolyte
Joined: 29 Sep 2005
Posts: 51
|
By 'no luck', I meant that I am seeing same error msg (ofcourse, object type ic execution group)
Its new implementation so I wanted to restrict the deploy access but would like to give them stop/start flow access |
|
| Back to top |
|
|
|
|
