| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| LDAP security setup recommendations |
« View previous topic :: View next topic » |
| Author |
Message
|
| marxgp |
 Posted: Tue Aug 20, 2019 2:36 am Post subject: LDAP security setup recommendations |
 |
|
Newbie
Joined: 19 Aug 2019
Posts: 3
|
Hi
We are looking at implementing MQ with LDAP on our new Linux server and was hoping for some recommendations with regards to access given to groups and principals.
Option 1 would be to create 3 primary groups in LDAP namely:
mq_QM1_Users - any user that want access MQ and then give permission to specific objects like a queue or a channel on principle level
mq_QM1_App_ids - any application id that need access to MQ and then give permission to specific objects like a queue or a channel on principle level
mq_QM1_mqm - users that need to manage MQ with full rights given on group level.
Option 2 would be to define groups in LDAP with each one providing a specific access for each object starting with a specific prefix. We would then have for example for queues TEMP.REQUEST and TEMP.RESPONSE the groups mqm_QM1_q_TEMP_put, mqm_QM1_q_TEMP_get, mqm_QM1_q_TEMP_set, etc. Users would then be put in these groups in LDAP and access in MQ would be given on group level only
i.e. setmqaut -m QM1 -n TEMP.** -t q -g mqm_QM1_q_TEMP_put +put
Option 3 would be to create application groups in LDAP for example mqm_QM1_HR which would group all the access for the HR objects. This would include queues, channels, etc.
Thanks
Marco |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Aug 20, 2019 4:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20729
Location: LI,NY
|
Hi Marco, looking at your post just a little FYI
Does not matter what permissions you assign to group mqm, by definition group mqm has all rights. Now I hope you don't have 2 groups mqm (one local and one on LDAP) because that would confuse the crap out of everything... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| markt |
| Posted: Tue Aug 20, 2019 6:14 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
| Quote: |
| by definition group mqm has all rights |
Not when you're using LDAP authorisation |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 20, 2019 11:47 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20729
Location: LI,NY
|
| markt wrote: |
| Quote: |
| by definition group mqm has all rights |
Not when you're using LDAP authorisation |
Only because you installed with local mqm and not ldap mqm. There is a difference in the GID hence the difference in authorizations!
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| markt |
| Posted: Wed Aug 21, 2019 12:04 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
There is no such thing as an "LDAP mqm". All LDAP groups would have a full Distinguished Name. MQ does not automatically grant full access to any LDAP group (whether or not its record has a subfield containing just 'mqm')
If you happen to be using something like Centrify that extends /etc/passwd, /etc/group via the nsswitch mechanism to make it look as though entries defined in an LDAP directory are really "local" users and groups by mapping fields from the LDAP record to a single name and GID, similarily to a NIS server, then you are not going to be using MQ's LDAP authorisation model but its traditional OS authorisation.
It's solutions like Centrify where people may end up with two groups of the same name but different GIDs. MQ's LDAP authentication and authorisation is independent of those OS resources.
The only use of a local OS resource is for the USER - not GROUP - who started the qmgr (and on Windows a couple of other special accounts). |
|
| 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
|
|
|
|
