diff options
| author | Jakub Hrozek <jhrozek@redhat.com> | 2013-01-06 16:04:54 +0100 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2013-01-09 17:59:28 +0100 |
| commit | a26dfbfdd5a325acd85f4f339587365f29810342 (patch) | |
| tree | fdf7956bb72d6b1d9dee71850230b8f21f8b8204 /src/db/sysdb_services.c | |
| parent | f9f74a587c8e96dcf90214c760022684afc8bef7 (diff) | |
| download | sssd-a26dfbfdd5a325acd85f4f339587365f29810342.tar.gz sssd-a26dfbfdd5a325acd85f4f339587365f29810342.tar.xz sssd-a26dfbfdd5a325acd85f4f339587365f29810342.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/db/sysdb_services.c')
0 files changed, 0 insertions, 0 deletions