| Author |
Message
|
| Vitor |
 Posted: Thu May 31, 2007 5:13 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ah - PUTAUT!
I did know that.... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| oomran |
| Posted: Thu May 31, 2007 5:21 am Post subject: |
|
|
Novice
Joined: 19 Feb 2007
Posts: 16
|
| is there a quick article on how to use the MCA? |
|
| Back to top |
|
|
| oomran |
| Posted: Thu May 31, 2007 5:47 am Post subject: |
|
|
Novice
Joined: 19 Feb 2007
Posts: 16
|
I tried to set the MCA UserID to 'omahmoud' on the reciever channel
and the putaut property to context
but when I send from the server side the message send normally |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 31, 2007 5:53 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu May 31, 2007 6:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
PUTAUT(CTX) is contradictory to MCAUSER. MCAUSER says "everything that comes over this channel is authorized as *this* user".
PUTAUT(CTX) says "everything that comes over this channel is authorized as whatever user is in the MQMD".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| oomran |
| Posted: Thu May 31, 2007 6:31 am Post subject: |
|
|
Novice
Joined: 19 Feb 2007
Posts: 16
|
| also I tried to set the putaut to context and did not set any user in the MQMD but the message also sent. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 31, 2007 6:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| oomran wrote: |
| also I tried to set the putaut to context and did not set any user in the MQMD but the message also sent. |
From the Application Programming Reference:
| Quote: |
| This field is normally an output field generated by the queue manager but for an MQPUT or MQPUT1 call you can make this field an input/output field and specify the UserIdentification field instead of letting the queue manager generate this information. Specify either MQPMO_SET_IDENTITY_CONTEXT or MQPMO_SET_ALL_CONTEXT in the PutMsgOpts parameter and specify a userid in the UserIdentifier field if you do not want the queue manager to generate the UserIdentifier field for an MQPUT or MQPUT1 |
So if you don't set it, and don't set context, the queue manager fills it in.
You might get value from spending some time working through the AP & security manuals working out a strategy, rather than changing settings in the hope you'll hit the right combination. Though you might of course. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
