ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexIBM MQ API SupportC# MQClient getting 2035 not authorized

Post new topicReply to topic
C# MQClient getting 2035 not authorized View previous topic :: View next topic
Author Message
anb.salim
PostPosted: Thu Dec 29, 2016 6:58 am Post subject: C# MQClient getting 2035 not authorized Reply with quote

Newbie

Joined: 15 Dec 2016
Posts: 2

We are facing a problem of connectivity from C#.Net MQClient as it returning an error saying 2035 Not Authorized. As we know that once we set the MCAUSER, it is working fine. But based on our security policies doesn't allow to set the MCAUser. So kindly advise the resolution method to resolve the connectivity issue.

Below is our code sample:

Code:

                case MQC.TRANSPORT_MQSERIES_BINDINGS:
                    break;
                case MQC.TRANSPORT_MQSERIES_CLIENT:
                case MQC.TRANSPORT_MQSERIES_XACLIENT:
                case MQC.TRANSPORT_MQSERIES_MANAGED:
                    connectionProperties.Add(MQC.HOST_NAME_PROPERTY, hostName);
                    connectionProperties.Add(MQC.PORT_PROPERTY, "11006");
                    connectionProperties.Add(MQC.CHANNEL_PROPERTY, channel);
                    connectionProperties.Add(MQC.USER_ID_PROPERTY, "wasadm");
                    connectionProperties.Add(MQC.PASSWORD_PROPERTY,"");
                    connectionProperties.Add(MQC.CONNECT_OPTIONS_PROPERTY, MQC.MQCNO_RECONNECT);
                    break;
            }


                MQQueueManager qMgr = new MQQueueManager(qManager, connectionProperties);
               
                // Set up the options on the queue we want to open
                //int openOptions = MQC.MQOO_OUTPUTMQOO_INPUT_AS_Q_DEF | MQC.MQOO_OUTPUT;
                int openOptions = MQC.MQOO_OUTPUT;

               // memcpy(md.Format, MQFMT_STRING, (size_t)MQ_FORMAT_LENGTH);
               // memcpy(md.MsgId, MQMI_NONE, sizeof(md.MsgId));

                // Now specify the queue that we want to open,and the open options
                MQQueue system_default_local_queue =
                  qMgr.AccessQueue("ClntNatheerWatchListRq", openOptions);
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Dec 29, 2016 8:47 am Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6077
Location: Somewhere over the Rainbow this side of Never-never land.

From your description you must be using MQ 8.
You will have to make the QMGR allow your connection even though the QMGR rules spectify that one must be given.

So, you have to Either

Get the security policy changed. The User/Password you supply just has to be a valid one, not an Admin one. In fact you should not use an admin one at all.

or

Get your MQ Admins to setup access to that Client channel (SVRCONN) that allows connections from clients without a user supplied and then the definition would make the connection with a valid username/password.

or

Change the QMGR to accept all connections regardless of the username/password supplied.

or

a combination of the above.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Dec 29, 2016 10:46 am Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 7795
Location: US: west coast, almost. Otherwise, enroute.

Of course, that's just a guess since you provided no useful information, such as:
- MQ version/release
- client o/s version/release
- MQ client version/release
- is this a new app?
- has this ever worked before?
- what has changed?
That kind of stuff.
_________________
I didn't know that Schrdinger had a cat.
Back to top
View user's profile Send private message
anb.salim
PostPosted: Sun Jan 08, 2017 11:45 pm Post subject: Reply with quote

Newbie

Joined: 15 Dec 2016
Posts: 2

Gentlemen, then for the response. Please find the below requested details:

- MQ version/release
    Name: WebSphere MQ
      Version: 8.0.0.2

      Level: p800-002-150217.2

      BuildType: IKAP - (Production)

      Platform: WebSphere MQ for HP-UX (Itanium platform)

      Mode: 64-bit

      O/S: HP-UX B.11.31


    - client o/s version/release
      Windows 7 Enterprise


    MQ client version/release
      8.0.0.2

      CMVC level: p800-002-150217.2_KAP


    - is this a new app? Yes
    - has this ever worked before? - No


    Please let us know if you need any other details.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Mon Jan 09, 2017 2:12 am Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6077
Location: Somewhere over the Rainbow this side of Never-never land.

What about the points I made in my original response?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexIBM MQ API SupportC# MQClient getting 2035 not authorized
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.