| Author | Message | 
		
		  | predmond | 
			  
				|  Posted: Thu Mar 27, 2014 8:50 pm    Post subject: MQRC_NOT_AUTHORIZED but have connect authorisation.. |   |  | 
		
		  | Newbie
 
 
 Joined: 27 Mar 2014Posts: 3
 
 
 | 
			  
				| Trying to use a .broker file to connect & create a new execution group/ integration server with the below command.. 
 mqsicreateexecutiongroup -n ESBIBDEV1_NODE.broker -e NEW
 
 which fails with a 2035 / MQRC_NOT_AUTHORIZED
 
 BIP1046E: Unable to connect with the queue manager (The user 'predmond' is not a
 uthorized to connect to queue manager 'ESBIBDEV1_QM' (MQ reason code 2035 while
 trying to connect)).
 
 
 .broker file is generated from MQExplorer (right clicking node, export for remote con..), I'm a local admin & have ran mqsisetsecurity so are a member of mqm & mqbrkrs.
 
 using the dspmqaut command to show what my user account has shows that I do have connect etc privileges.
 
 dspmqaut -m ESBIBDEV1_QM -t qmgr -p predmond
 gives:
 Entity predmond has the following authorizations for object ESBIBDEV1_QM:
 inq
 set
 connect
 altusr
 crt
 dlt
 chg
 dsp
 setid
 setall
 ctrl
 system
 
 Thinking I should be able to connect but must be missing something..
 
 Any thoughts on what I'm missing?
 
 Here's what's in the generated .broker file for connecting
 
 <?xml version="1.0" encoding="UTF-8"?>
 <configmgr crlNameList="" domainName="" host="10.243.3.50" listenerPort="1414" queueManager="ESBIBDEV1_QM" securityExit="" securityExitJar="" sslCipherSuite="NONE" sslDistinguishedNames="" sslKeyStore="" sslTrustStore="" svrconn="SYSTEM.BKR.CONFIG"/>
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | predmond | 
			  
				|  Posted: Thu Mar 27, 2014 8:54 pm    Post subject: Have privileges to SYSTEM.BROKER.ADMIN.QUEUE too |   |  | 
		
		  | Newbie
 
 
 Joined: 27 Mar 2014Posts: 3
 
 
 | 
			  
				| dspmqaut -m ESBIBDEV1_QM -t q -n SYSTEM.BROKER.ADMIN.QUEUE -p predmond Entity predmond has the following authorizations for object SYSTEM.BROKER.ADMIN.
 QUEUE:
 get
 browse
 put
 inq
 set
 crt
 dlt
 chg
 dsp
 passid
 passall
 setid
 setall
 clr
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | exerk | 
			  
				|  Posted: Thu Mar 27, 2014 10:55 pm    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 02 Nov 2006Posts: 6339
 
 
 | 
			  
				| What version of WMQ? If => V7.1 do you have CHLAUTH enabled? _________________
 It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | hughson | 
			  
				|  Posted: Sat Mar 29, 2014 5:37 am    Post subject: |   |  | 
		
		  |  Padawan
 
 
 Joined: 09 May 2013Posts: 1967
 Location: Bay of Plenty, New Zealand
 
 | 
			  
				| With all errors emitted by MQ, please remember to look at your queue manager error log for additional details. If you are being blocked by CHLAUTH as exert has postulated, it will say so. If it is some other reason, it will say so. There is no point in trying to guess, just read the information the queue manager is giving you. 
 Cheers
 Morag
 _________________
 Morag Hughson @MoragHughson
 IBM MQ Technical Education Specialist
 Get your IBM MQ training here!
 MQGem Software
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | predmond | 
			  
				|  Posted: Sun Mar 30, 2014 3:51 pm    Post subject: |   |  | 
		
		  | Newbie
 
 
 Joined: 27 Mar 2014Posts: 3
 
 
 | 
			  
				| Version is 7.5.0.1 
 For the test env I'm using I have switched off with a ALTER QMGR CHLAUTH(DISABLED)
 
 Will look into the correct settings for prod.
 
 Thanks for putting me on the right track.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |