summaryrefslogtreecommitdiffstats
path: root/src/providers/ldap/ldap_init.c
diff options
context:
space:
mode:
authorJakub Hrozek <jhrozek@redhat.com>2013-01-06 16:04:54 +0100
committerJakub Hrozek <jhrozek@redhat.com>2013-01-09 17:48:54 +0100
commitc3f785d5bd5c52b3498ac8d9ed9b671bd3bb5021 (patch)
treeb835e69bfb14aaf44b898b7250a79d1c6dc63d6e /src/providers/ldap/ldap_init.c
parentf8f2ec0b4097bef628e66919acb746fe0ef6f6c2 (diff)
downloadsssd-c3f785d5bd5c52b3498ac8d9ed9b671bd3bb5021.tar.gz
sssd-c3f785d5bd5c52b3498ac8d9ed9b671bd3bb5021.tar.xz
sssd-c3f785d5bd5c52b3498ac8d9ed9b671bd3bb5021.zip
AD: Add user as a direct member of his primary group
In the AD case, deployments sometimes add groups as parents of the primary GID group. These groups are then returned during initgroups in the tokenGroups attribute and member/memberof links are established between the user and the group. However, any update of these groups would remove the links, so a sequence of calls: id -G user; id user; id -G user would return different group memberships. The downside of this approach is that the user is returned as a group member during getgrgid call as well.
Diffstat (limited to 'src/providers/ldap/ldap_init.c')
0 files changed, 0 insertions, 0 deletions