ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » MQ client and user authentication

Post new topic  Reply to topic
 MQ client and user authentication « View previous topic :: View next topic » 
Author Message
lhotari
PostPosted: Wed Mar 05, 2008 7:20 am    Post subject: MQ Java TCP/IP client uses "user.name" as MQ crede Reply with quote

Newbie

Joined: 25 Oct 2006
Posts: 5
I started the Java client with a system property "user.name=SYSTEM" and I got rid of MQJMS2013 problems.
MQ Java client in CLIENT (tcp/ip) transportType mode relies on the user.name System property for the MQ credential.

for example:
java -Duser.name=SYSTEM SomeClass

The full explanation:
http://www.topsecurity.dk/cmview/View?id=1575

Actually this problem was in WAS 6.1 and the system property can be added for the application server in WAS admin console at "application server -> process definition -> JVM -> custom properties".
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Mar 05, 2008 3:04 pm    Post subject: Re: MQ Java TCP/IP client uses "user.name" as MQ c Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
Split from previous topic as it was obviously intended for a different one...

lhotari wrote:
I started the Java client with a system property "user.name=SYSTEM" and I got rid of MQJMS2013 problems.
MQ Java client in CLIENT (tcp/ip) transportType mode relies on the user.name System property for the MQ credential.

for example:
java -Duser.name=SYSTEM SomeClass

The full explanation:
http://www.topsecurity.dk/cmview/View?id=1575

Actually this problem was in WAS 6.1 and the system property can be added for the application server in WAS admin console at "application server -> process definition -> JVM -> custom properties".


I would never condone such a setup.
Use JAAS to create an authentication alias and use it when defining the connection Factory in JNDI. This is the right way to go. You do not want to force your JVM to run under some specific user name...

In a standalone client use the following form of connect
Code:
(q)cf.createConnection(username, password);


Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » MQ client and user authentication
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.