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 » General IBM MQ Support » Keeping MCAUser blank

Post new topic  Reply to topic
 Keeping MCAUser blank « View previous topic :: View next topic » 
Author Message
magkids
PostPosted: Thu Aug 09, 2007 2:37 am    Post subject: Keeping MCAUser blank Reply with quote

Newbie

Joined: 09 Aug 2007
Posts: 8

I want to ask what are the consequences of leaving MCAUser blank? Provides that I have use SSL or Channel Exit, only authenticate user can access the queue manager.

If I leave MCAUser blank, that means the user can access with admin rights. Can the user create/delete queues through the channel? How? (Aren't these functions should be done by SVR.ADMIN.CONN channel?)
Thanks a lot.
Back to top
View user's profile Send private message
jeevan
PostPosted: Thu Aug 09, 2007 7:35 am    Post subject: Reply with quote

Grand Master

Joined: 12 Nov 2005
Posts: 1432

If you have setup MCAUSER( let's say mqm)) and some one knows the name of your server connection channel that has an MCAUSER, he/she can connect to your qmgr with the permission of the MCAUSER(mqm in this case). This does not require the incoming user to be in mqm group and admin group ( in windows) and mqm group in unix. You can guess what happens then.

So, it is advaisable to leave MCAUSER blank and authorise individual ( better create a group and put similar user together and authorise the group for certain object they need to work with ). This way you can protect your MQ system.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Aug 09, 2007 7:39 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

If you leave the MCAUser blank, then you are trusting that whomever connects to your channel has properly authenticated the user that they are presenting.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
magkids
PostPosted: Thu Aug 09, 2007 5:51 pm    Post subject: Reply with quote

Newbie

Joined: 09 Aug 2007
Posts: 8

I know the incoming user can then access as mqm user. But aren't the channel should be an application channel? So he could only do something like put, get message. Any admin rights like create/delete queue should be done through SVR.ADMIN.CONN channel. If I protect the SVR.ADMIN.CONN channel, so is it means that I do not need to set MCAuser?
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Aug 10, 2007 2:04 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

There is no difference between any SVRCONN channel.

SYSTEM.ADMIN.SVRCONN is just a default channel.

Any SVRCONN can be used to talk to any queues, including the Command Server input queue.

I repeat.

If you DO NOT SET the MCAUser, then you are TRUSTING that the client side of the channel has PROPERLY AUTHENTICATED the user that the channel is presenting.

This might actually be okay in your organization. It depends entirely on your policies and configurations.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Keeping MCAUser blank
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.