MQSeries.net :: View topic - Authentication, Authorisation, Integrity and Non-repudiation

friedl.otto

I have made some superficial enquiries on this topic in the past.

From these arose the following fairly obvious factoids:

1. SSL ensures 'Data Integrity' between two queue managers.

2. MCAUSER can be sidestepped by means of JVM args, and is thus
effectively useless for Authentication.

*Dons the Carbon Wool suit and Lead Apron*

Since I have never worked on an IBM WebSphere MQ Extended Security
Edition queue manager, and have not found volumes of documentation
detailing the low-down ... could someone (preferably of a Java bent)
perhaps enlighten me.

1. Since we all want X/A, which requires native bindings, how does the
"Extended Security" impact the classic MQ_GET Java code?

2. Can user-level access be managed on all MQ "Objects".

3. Am I dreaming if I mention group-level access?

We may soon be getting licensing for "Extended Security", I would like to
at least put in a brave effort at doing proper end-to-end MQ security with
at least a concerted push toward proper authentication, decent
authorisation, solid data integrity and if at all possible some whiff of non-
repudiation.

_________________
Here's an idea - don't destroy semaphores unless you're certain of what you're doing!

-- Vitor