You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 I think 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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1961
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 I think 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.
Comments
Comment from sbose at 2013-06-04 21:06:13
Fields changed
design: => https://fedorahosted.org/sssd/wiki/DesignDocs/IPAServerMode
Comment from sbose at 2013-06-12 11:18:27
Fields changed
owner: somebody => sbose
status: new => assigned
Comment from dpal at 2013-06-27 16:29:27
A sub ticket of the 1.11 feature.
rhbz: => 0
Comment from jhrozek at 2013-06-28 19:36:22
Fields changed
patch: 0 => 1
Comment from jhrozek at 2013-06-28 20:37:19
resolution: => fixed
status: assigned => closed
Comment from sbose at 2017-02-24 15:04:18
Metadata Update from @sbose:
The text was updated successfully, but these errors were encountered: