| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ using a userid of ‘SYSTEM’ by default |
« View previous topic :: View next topic » |
| Author |
Message
|
| PT-smc |
 Posted: Tue Feb 03, 2009 5:56 pm Post subject: MQ using a userid of ‘SYSTEM’ by default |
 |
|
Newbie
Joined: 03 Feb 2009
Posts: 1
|
Hi,
I was hoping you could help me with something possibly simple, being a newbie to mq server configuration.
In summary, below shows that the Client can successfully connect to MQ server and execute messages via a middleware adaptor. Which means that the installation & use of the MQ Client v6 software is successful, after upgrading from version 5 recently.
But what i want is to change the default userid from "SYSTEM" to PIVR instead. We have multiple Clients that connect at once and need to be able to differentiate them. Is there an envornmental cmd that I can use or
what's the best way to define a userid and will it hold after a restart?
I have looked everywhere for this feature which was never in version 5.
MQ server side drop info:
2009-02-03|16:38:02|Connection accepted, Channel [IVR.CH] ConName [*.*.*.*] Flags [BlockMqmUsers=Y AllowBlankUserID=Y UseridUpperLowerCase=* ] User [SYSTEM]
2009-02-03|16:38:02|CON Set MCA userid to [mqm] from [SYSTEM] [i2 e16]
2009-02-03|16:38:02|Connection accepted, Channel [IVR.CH] ConName [*.*.*.*] Flags [BlockMqmUsers=Y AllowBlankUserID=Y UseridUpperLowerCase=* ] User [SYSTEM]
Note: The "[*.*.*.*]" designates the Ip address of the client machine.
Thanx in advance. |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Feb 03, 2009 11:54 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Are you using BlockIP/BlockIP2? What is the 'middleware adaptor'? What is the platform?
Generally accepted wisdom is to define a SVRCONN per client and use MCAUSER per channel, where the MCAUSER ID (especially as you are allowing connection with a blank userid - plenty of discussion on this board as to why that is not a good idea) is locked down to the specific objects the 'client' needs - and the 'client' should be started up under the appropriate ID. Connection can then be set using the MQSERVER variable (can't lock down with SSL) set by the client application when it starts, or by defining a Client Channel Definition Table (can be locked down with SSL).
I'm guessing that the middleware adaptor, or client application that invokes it, does so as SYSTEM because that'll ensure it works...Windows by any chance? 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| 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
|
|
|
|
