| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Help with authorization MCA |
« View previous topic :: View next topic » |
| Author |
Message
|
| Artemio |
 Posted: Fri Oct 10, 2003 10:46 am Post subject: Help with authorization MCA |
 |
|
Novice
Joined: 11 Sep 2003
Posts: 21
|
I can't connect to other machine by error code 2035, and I only connected when I'm in the same machine, so in the documentation mencioned something about of MCA, How I can do to set MCA permision?
How can I configure with the MCA my channel????
Can I set this Id User in code with MQCD structure??? and How I do this???
Thanks! |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Fri Oct 10, 2003 10:58 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Need more info....
You did not mention as to what type of channel is involved and what type of security/permissions we are talking about. From what i understand i guess you are talking about Svrconn channel and MCAUSER. When you set this attribute, MQ authenticates any calls using this userid. Hence you have to make sure you have the appropriate authority assigned to this userid that you use within the MCAUSER attribute.
Cheers
Kumar |
|
| Back to top |
|
|
| xmitq |
| Posted: Tue Oct 14, 2003 4:37 am Post subject: |
|
|
Novice
Joined: 07 Oct 2003
Posts: 16
Location: London
|
To connect to a Queue manager on another platform, such as Solaris, we ensure that a svrconn channel is defined
def CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN) MCAUSER(userid)
The userid is a user id on the other platform (Solaris). It is this user id that is authenticated when the channel starts.
We use this facility when using the MQEXPLORER to control/configure distributed Queue Managers.
Hope this helps. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Tue Oct 14, 2003 5:08 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Still not really clear with your question. Reason.
If you explicitly mention the userid in MCAUSER attribute and you have a valid principal/userid on the remote end(Solaris), then the authority checking is NOT done using the userid that comes in on a connect, but instead it is ALWAYS the userid in this MCAUSER attribute. Hence irrespective of what machine and logon id you use to access this channel, you should be able to connect to this qm without any issues. Provided the userid mentioned in MCAUSER attribute has all the appropriate authorizations.
Hence to assist you further, please post your detailed scenarios with the userids that are defined, their authorizations, the logon ids that you use on both the systems.
Cheers
Kumar |
|
| 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
|
|
|
|
