| Author |
Message
|
| nageshr99 |
 Posted: Thu Jun 29, 2017 8:54 pm Post subject: Getting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error |
 |
|
Novice
Joined: 30 May 2017
Posts: 24
|
Hi,
We are getting the error as shown below:
"Getting - 2035 - 0x0000007f3 MQRC_NOT_AUTHROIZED error " - when we run the execution file of the sample C++ program - imqsputc.cpp after compilation using GCCver 4.8.5 on linux scientific version 7.2.
Its a 64 bit - non threaded compilation.
we run the sample program using the below command:
imqsputc_64 q1 qm1 'svrch1/tcp/192.168.2.226(1414)'
where q1=input parameter 1 - local q created using MQ explorer version 8.0
where qm1 = input parameter 2 - Queue manager created using MQ explorer version 8.0
where 'svrch1/tcp/192.168.2.226(1414)' = input parameter 3- which mentions the server-connection channel name along with protocoltype/IP address/portnumber - which is created using MQ explorer version 8.0
Pls let us knw how to resolve this issue.
Thanks. |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Thu Jun 29, 2017 10:39 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
...and do you think you ought to be authorised to connect to this Queue Manager ? What authentication is it using ? It is an MQ v8 Queue Manager so CHLAUTH is in force....or have you switched it off ? Does this Queue Manager just allow anybody to connect ? Clearly that is not a good idea in the long term.
It might be better to give us the details you do know and what you've tried rather than just asking everyone what is wrong.
MQ Security is quite a big subject. Luckily there are lots of blogs about which give guidance on configuring MQ authorities and authentication. If you just Google 'MQ Authentication' you'll find quite a few hits.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Jun 30, 2017 6:56 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1237
Location: Gold Coast of Florida, USA
|
@PaulClarke,
I will risks being too big for my pants...
Just because MQ Explorer 8 is in use, does not mean the Qmgr is V8.
dspmqver output from the Qmgr would be helpful as a starter.
The following would also be helpful (replace <QmgrName> with the actual Qmgr name):
echo dis qmgr|runmqsc <QmgrName> |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 30, 2017 10:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20729
Location: LI,NY
|
So you got a not authorized response...
Why would you have expected anything else??
Did you do anything at all to obtain authorization?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nageshr99 |
| Posted: Sun Jul 02, 2017 8:12 pm Post subject: |
|
|
Novice
Joined: 30 May 2017
Posts: 24
|
Thanks.
It finally some how worked after executing the below command:
ALTER QMGR CHLAUTH(DISABLED) CONNAUTH(' ')
REFRESH SECURITY TYPE(CONNAUTH) |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Sun Jul 02, 2017 8:17 pm Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Bear in mind that CHLAUTH is there for a reason. The correct solution to security problems is rarely to just switch off the check.
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| nageshr99 |
| Posted: Mon Jul 03, 2017 7:50 pm Post subject: |
|
|
Novice
Joined: 30 May 2017
Posts: 24
|
| PaulClarke wrote: |
Bear in mind that CHLAUTH is there for a reason. The correct solution to security problems is rarely to just switch off the check.
Cheers,
Paul. |
infact this CHLAUTH command alone did not work.CONNAUTH(' ') command along with the REFRESH SECURITY TYPE(CONNAUTH) command did the trick. |
|
| Back to top |
|
|
|
|
