| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Secure queue + correlation ID |
« View previous topic :: View next topic » |
| Author |
Message
|
| telesguilherme |
 Posted: Fri May 16, 2014 2:42 pm Post subject: Secure queue + correlation ID |
 |
|
Acolyte
Joined: 16 Feb 2008
Posts: 56
|
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Fri May 16, 2014 3:58 pm Post subject: Re: Secure queue + correlation ID |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| telesguilherme wrote: |
| I'm trying to accomplish the implementation of a security level GET / PUT based on CorrelationID. |
Not possible.
| telesguilherme wrote: |
| It is possible to restrict the GET of a message, only when we specify the attribute CorrelationID? |
Yes, you can get a message by specifying a Correlation ID but it has nothing to do with security.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| tczielke |
| Posted: Fri May 16, 2014 4:45 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
| I would think you could technically do this on the distributed platforms with an API exit, but what are your requirements that would require you to do this? |
|
| Back to top |
|
|
| telesguilherme |
| Posted: Sat May 17, 2014 3:46 am Post subject: |
|
|
Acolyte
Joined: 16 Feb 2008
Posts: 56
|
Dear all,
Thanks for the repply.
My requirements are that a single user/application cannot get any message without specifying the correlationid. Because i think it is still possible to get any message without that specification on the "get request". |
|
| Back to top |
|
|
| tczielke |
| Posted: Sat May 17, 2014 4:43 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
If your platform is distributed, you may want to review the API exit.
http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.dev.doc/q027920_.htm
Especially, note the following:
| Quote: |
| For security, you can provide authentication, checking that applications are authorized to access a queue or queue manager. You can also police applications' use of the API, authenticating the individual API calls, or even the parameters they use. |
|
|
| 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
|
|
|
|
