Geez. Everything was fine until you had to tell everyone that Java has no security as a client.
Actually this is well known and if you search the list archives you will find many threads on the subject with suggested solutions, with security exits being one solutions. If you have MQ 5.3 you can use the new SSL security too and require the client have a certificate to access the queue manager.
BTW, you mention adding a client ID to the mqm group but that is about the same as no security at all.
Mike Murphy
Sr. Middleware Consultant
MQ Solutions, LLC
http://www.mqsolutions.com
"Narasimha reddy.V" <[EMAIL PROTECTED]> wrote:
|
Date Recieved:
| 01/05/2003 11:48:03 AM | |
|
To:
| [EMAIL PROTECTED] | |
|
cc:
| ||
|
Bcc
| ||
|
Subject:
| Queue Manager security problem java client |
Hi All
I am having a java client application for MQSeries written
using Java Classes API
Here my problem is my MQServer is not asking any client authentication!!
But in general any other applications like c,c++ needs client authenticatin with MQServer(like Adding client user id to MQM group of MQServer).
Now my serious problem is, any Java non authenticated client application will able to connect my MQ Manager!!!
Why MQEnvironment.userid and MQEnvironment.password parameters are optional in java classes?
Why no restriction for java client?
Have you any body faced this type of problem?
Could please help me how to restrict the clients for my QM??
Or Do I need to implement Channel Security exits for Java client?
Regards
Reddy
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
