| Author |
Message
|
| Yanghui |
 Posted: Mon Sep 30, 2002 5:25 am Post subject: MCAUSER on both sender and receiver channels |
 |
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
I am very confused about how to use MCAUSER on both sender and receiver channels. It would be great if somebody can help me regarding to the below questions.
1. Should I use MCAUSER same on the both ends of a sender-receiver channel? Can I use them seperately for different functions?
2. From manual, MCAUSER should precede the log-on user id to be used for security check. But I couldn't prove this. The test I did was to send a message from one qm to another. The both MCAUSERs were setup as a none MQ access user id. However, the message still was delivered to the destination q successfully. I think the application log-on user id must be used for security check or the MCAUSERs setup didn't take effect even after qm restart. Something I am missing here?
3. I am wondering if MCAUSER setup can change the user id in MQMD of the message or it's only used for security check?
4. How should I use Put Authority when MCAUSERs are setup?
Many thanks in advance.
Best regards
-Yanghui |
|
| Back to top |
|
 |
| dgolding |
| Posted: Tue Oct 01, 2002 2:08 am Post subject: |
|
|
Yatiri
Joined: 16 May 2001
Posts: 668
Location: Switzerland
|
| I would expect the RECEIVER end of channel would override the SENDER end MCAUSER. Use "setmqaut" to set the authorities for the receiver MCAUSER user ID. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Oct 01, 2002 3:35 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Well 2 things
1) When you set the MCAUSER on a channel that is the userid used regardless of who the messages come from.
2) The receiver channel has a PUT AUTHORITY attribute it can be
either default or context. default means it will use the userid that the
receiver channel was started with. context will be based on the userid encoded in the message provided that the MCAUSER attribute isnt set.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Yanghui |
| Posted: Tue Oct 01, 2002 6:44 am Post subject: |
|
|
Disciple
Joined: 08 May 2002
Posts: 151
Location: Dublin, Ireland
|
Hi, Jeff,
Thanks for your response.
Does your first point mean the user id in MQMD will be replaced by MCAUSER when a message flows from sender to receiver channel with MCAUSER setup? I just couldn't see this happen in my system. No matter what change I made in MQ, it seemed to me that MCAUSER always been ignored and made no difference to the whole process.
I don't know if any other setup I should do before MCAUSER takes effect. Did you make MCAUSER work before? Is there anybody who did? Can you let me know how?
Many thanks again. |
|
| Back to top |
|
|
| mrlinux |
| Posted: Tue Oct 01, 2002 7:06 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
No the MQMD user info will always be the same. The question comes into play when the receiver channel determines what authority to use to put the message on the queue.
1) The receiver channel putauth attribute is set to DEFAULT, it will use the authority it was started with (usally mqm) to issue the MQPUT (Channel programs are just MQSeries apps) .
2) If set to CONTEXT and the MCAUSER is NOT SET, then the userid in the MQMD will be used to write to the queue.
3) if set to context and the MCAUSER is set then the userid in the MCAUSER field is used.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Oct 02, 2002 10:14 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Not sure what platform you're dealing with but on OS/390 if you specify ONLYMCA for PUTAUT it will definitely override any ID coming across with the ID in MCAUSER.
Steve |
|
| Back to top |
|
|
|
|
