Outside of the scope of MQ maybe but depending on the data you should
conisder controlling data access through key ranges. Within MQ itself
possibly consider using separate queues per client to avoid possible
misdirection of messages and its easier to control access. Also look at the
message exit if you want to do some kind of security related data
validation.
Regards
Tim A
"DeBlassio, Joe"
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
-MINOR.COM> cc:
Sent by: MQSeries Subject: Security Implementation
for a reusable java client
List
<[EMAIL PROTECTED]
C.AT>
07/03/2003 06:48
Please respond to
MQSeries List
List,
I'd like to ask for suggestions on security implementation for a reusable
java client program.
This program would be distributed to customers for the purpose of sending
messages to a queue manager on a DMZ.
I'm thinking SSL is a given, but as far as authentication and controlling
access, what would folks recommend as essential in terms of security
implementation? The goal would be to reuse the client program among
several customer, but to set unique security parms for each customer.
Thanks, Joe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
