On 13 Sep 2015, at 01:09, Ray Van Dolson <rvandolson(a)esri.com>
Trying to finalize a standard setup for access control and finding
there are numerous options for group or username based access control.
I'm using the ad access_provider (2012 R2 servers).
Hi Ray, thanks for the very nice summary. I think we should add it to our upstream AD
+ Pros: Pretty powerful. I can do nested groups with the proper
syntax. Good speed?
Umm, can you? I always thought the memberof attribute in AD's user entry was
single-level? What configuration are you using?
- Cons: Configurations can get pretty ugly (especially with the
nested group ldap syntax) and complex all on one very long
line. Must be in the sssd.conf file so can't have thing
separated easily per-machine or per role that a machine may
- simple_allow_groups (with access_provider = simple)
+ Pros: Simple. Readable config.
- Cons: Not sure? Maybe some performance limitations as compared
to ad_access_filter? Don't believe supports nested group
It does. The biggest difference is that the ad_access_filter is applied on the LDAP entry
itself. In contrast, the simple provider first resolves the group memberships, saves them
to the cache and then evaluates the cached entry.
You're right that at the moment, the simple access provider can be a little slower,
unless ignore_group_members is set to true.
- pam_access (actually, not sure if this one works, but in theory it
Yes, I don't see a reason it shouldn't. I know several users tried this option.
+ Pros: Could externalize / customize per machine or per Ansible
role more easily due to ability to easily use multiple
external include files.
You can also set access per netgroup etc.
- Cons: Not sure. Another layer in the process so potentially
some delay and complexity.
- SSH's AllowGroups (should work with sssd-ad I believe?)
+Cons: Only works w/ SSH (maybe not a big deal for my use case).
Unsure on speed.
I would guess the performance would be similar to sssd's simple access provider. ssh
would retrieve the list of GIDs the user is a member of with getgrouplist() and then
convert the gid into name with getgrgid() which is cca what the simple access provider is
- ad_gpo_access_control (no idea how this one works but sounds
+Pros: In theory means everything is managed centrally in AD GPO.
Yes, this is the biggest win.
+Cons: I've never tried it so don't know. :-)
I would say the biggest con is that it's complex code that is not as well tested as
the other options simply because it has not been around as long as the others. There are
some bugs that were fixed in upstream only. But I would encourage you to try this option
and report bugs!
What SSSD version on what OS are you running?
Maybe I am missing some good alternatives above? Right now am using
ad_access_filter mostly and planning to use Ansible's templating system
to manage per host or service roles. Could get complex if we end up
needing to do customizations on a per machine basis in certain cases...
sssd-users mailing list