diff options
| author | Sumit Bose <sbose@redhat.com> | 2013-06-13 14:26:22 +0200 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2013-06-28 20:20:59 +0200 |
| commit | bfb40893be20b45279a40188cf16ef0eec1f9423 (patch) | |
| tree | db5d3d52216462f978117ca3c3c1207e68f34e06 /src/providers/ldap/sdap_async_users.c | |
| parent | 949fbc93defad394648b2651b43a7bbfa5bff42b (diff) | |
| download | sssd-bfb40893be20b45279a40188cf16ef0eec1f9423.tar.gz sssd-bfb40893be20b45279a40188cf16ef0eec1f9423.tar.bz2 sssd-bfb40893be20b45279a40188cf16ef0eec1f9423.zip | |
Allow different methods to find new domains for idmapping
Currently the range management code is in the generic LDAP provider and
can be used by the LDAP and AD provider. New ranges are allocated with
the help of a hash value of the domain SID.
If the IPA provider cannot find a range for a given domain it cannot
allocate a new range on its own but has to look up the idrange objects
on the FreeIPA server and use them accordingly. To allow the LDAP, AD
and IPA provider to use as much common code as possible a plugin
interface, similar to the one used to find the DNS site, to find a
missing range would be useful. The default plugin will be used by the
LDAP and the AD provider and the IPA provider will implement a plugin to
read the data from the server.
Fixes https://fedorahosted.org/sssd/ticket/1961
Diffstat (limited to 'src/providers/ldap/sdap_async_users.c')
0 files changed, 0 insertions, 0 deletions