diff options
author | Alexander Bokovoy <abokovoy@redhat.com> | 2015-12-23 15:04:40 +0200 |
---|---|---|
committer | Alexander Bokovoy <abokovoy@redhat.com> | 2015-12-23 16:30:16 +0200 |
commit | 2135375fa15cc992ed5b07781028440ce6220858 (patch) | |
tree | cf3dabc89df22d61c4b31c57cac07063512b8776 /tests/test22-schema-disable | |
parent | 38fc0024c2669006a4d71a722a75cf2aeeb3e4bf (diff) | |
download | slapi-nis-externalmembers.tar.gz slapi-nis-externalmembers.tar.xz slapi-nis-externalmembers.zip |
slapi-nis: add support to resolve external members of IPA groupsexternalmembers
FreeIPA allows to include external (non-LDAP) members into POSIX groups.
To define external members, an attribute ipaExternalMember is set to
the list of references to external members. Currently both FreeIPA and
SSSD support only references done with SIDs (Security Identifiers) from
the forests trusted by FreeIPA.
Resolving external members of FreeIPA groups requires resolving SIDs to
user and group names. However, since this resolution is already
implemented by SSSD for the group in question, slapi-nis can use the
fact that there is non-empty ipaExternalMember attribute's value to
trigger lookup of the FreeIPA group via SSSD and then copy over
memberUid attribute value set.
This logic requires that ipaExternalMember attribute value is present in
the entry to be put into the map cache. Thus, an additional
configuration is needed for the groups container:
schema-compat-entry-attribute: ipaexternalmember=%deref_r("member","ipaexternalmember")
Note that resolving external members of IPA groups requires to use
version of slapi-nis that populates the map cache after LDAP server
startup, as SSSD needs to talk back to the LDAP server in the process of
resolving external group members and that is not possible at the time
when slapi-nis plugin starts up as the LDAP server is not yet listenting
for incoming connections at that point.
Diffstat (limited to 'tests/test22-schema-disable')
0 files changed, 0 insertions, 0 deletions