| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| clarity about PassAllContext authority |
« View previous topic :: View next topic » |
| Author |
Message
|
| krypton |
 Posted: Wed Dec 05, 2018 7:10 am Post subject: clarity about PassAllContext authority |
 |
|
Disciple
Joined: 14 Mar 2010
Posts: 186
|
Hi, we are setting up a new environment for MQ and was looking for this Authority about "Pass All Context" and "Pass identity context" , Not able to determine whether application needs it or not.
the MQ documentation is not very clear on the definition of this authority-
| Quote: |
Pass all context Allow the application to pass all the context fields from the request message to a message that the application is putting on the queue |
.
Not clear what is allowed to the application here.
our model is our application team put message into a Request Remote Q and it goes to 3rd party system and get the response in a different Response local Q and application picks it up via SVRCONN channel.
So really not sure what this particular authority does? |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Dec 05, 2018 7:48 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Pass all and pass identity are well documented in the Development manual.
What isn't clear?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| krypton |
| Posted: Wed Dec 05, 2018 9:00 am Post subject: |
|
|
Disciple
Joined: 14 Mar 2010
Posts: 186
|
I have noticed another thing here -
on an existing working infrastructure, we have an ALIAS queue defined and following are the permission on that Alias Q for the application group
AUTHADD(BROWSE,DSP,GET,INQ,PUT,PASSALL,PASSID)
But I found out that the "TARGETQ" of this "ALIASQ" has no permission for the app group,
could it has something to do because we have set "PASSALL" on the Alias Queue?
_________________
Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 06, 2018 6:31 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| krypton wrote: |
I have noticed another thing here -
on an existing working infrastructure, we have an ALIAS queue defined and following are the permission on that Alias Q for the application group
AUTHADD(BROWSE,DSP,GET,INQ,PUT,PASSALL,PASSID)
But I found out that the "TARGETQ" of this "ALIASQ" has no permission for the app group,
could it has something to do because we have set "PASSALL" on the Alias Queue? |
No it just means that the app does not have permissions to put to the target /base queue directly and must use the ALIAS queue. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| krypton |
| Posted: Thu Dec 06, 2018 6:36 am Post subject: |
|
|
Disciple
Joined: 14 Mar 2010
Posts: 186
|
| fjb_saper wrote: |
| krypton wrote: |
I have noticed another thing here -
on an existing working infrastructure, we have an ALIAS queue defined and following are the permission on that Alias Q for the application group
AUTHADD(BROWSE,DSP,GET,INQ,PUT,PASSALL,PASSID)
But I found out that the "TARGETQ" of this "ALIASQ" has no permission for the app group,
could it has something to do because we have set "PASSALL" on the Alias Queue? |
No it just means that the app does not have permissions to put to the target /base queue directly and must use the ALIAS queue. |
thank you for the explanation.
I was only wondering if the App doesn't have permission on Target Q, then they will not be able to put in Alias Q as well.
My understanding was for an application to put message in Alias Q, they should have permission on both Alias Q as well as on Target Q.
Guess, I was wrong.
_________________
Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep. |
|
| Back to top |
|
|
| krypton |
| Posted: Thu Dec 06, 2018 6:43 am Post subject: |
|
|
Disciple
Joined: 14 Mar 2010
Posts: 186
|
| bruce2359 wrote: |
Pass all and pass identity are well documented in the Development manual.
What isn't clear? |
I think I got it, it means all application to pass identity context instead of QMGR/MQ deciding on MQ context, Am i correct to say so?
_________________
Dreams are not something which you watch when you are asleep,it is something which doesn't let you sleep. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Dec 06, 2018 6:56 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| krypton wrote: |
| bruce2359 wrote: |
Pass all and pass identity are well documented in the Development manual.
What isn't clear? |
I think I got it, it means all application to pass identity context instead of QMGR/MQ deciding on MQ context, Am i correct to say so? |
Not quite. This is not automatic. It means the application is allowed to pass all context. You have to research in which circumstances the app will attempt to do that whithout additional coding from you.
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
