| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Channel Security, Simple Question |
« View previous topic :: View next topic » |
| Author |
Message
|
| cturner |
 Posted: Sun Aug 03, 2003 9:10 pm Post subject: Channel Security, Simple Question |
 |
|
Newbie
Joined: 21 Aug 2002
Posts: 9
Location: Apex, NC
|
I have customers coming in through a sender/receiver pair. Each customer has their own queue or queues to put messages to. I'm going to put an MCA user ID on the receiver channel definition on my end and they will do the same on their end. Is there ANYTHING that the customers can do with this MCA user ID other than put messages to their queues? The ID will not even be created in the mqm group on my end. I just want to be sure they cannot do any type of administration or see other customer's information.
Thanks |
|
| Back to top |
|
 |
| EddieA |
| Posted: Mon Aug 04, 2003 7:21 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
What are you trying to achieve here as your suggestions don't really do anything. They do NOT provide any additional security.
If you just put the UserId in the MCA UserId and nothing else, then it will be ignored, as the default for Put Authority is Default. This means the messages are written to the queue under the MCA's authority.
If you change Put Authority to Context, then every message will be written using the UserId you have put in the MCA UserId, so as long as that user has permissions to the recipient queue, it will work. No matter who created the message.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| cturner |
| Posted: Mon Aug 04, 2003 7:42 am Post subject: |
|
|
Newbie
Joined: 21 Aug 2002
Posts: 9
Location: Apex, NC
|
We're trying to acheive a very simple security model. We have several customers using the same queue manager. We only want them to be able to put messages to only their queue and not be able to do any type of administrative commands on the queue manager.
At this point, we do not want to do SSL even though we are using V5.3 |
|
| 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
|
|
|
|
