Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Add plugin to LDAP provider to find new ranges #3003

Closed
sssd-bot opened this issue May 2, 2020 · 0 comments
Closed

[RFE] Add plugin to LDAP provider to find new ranges #3003

sssd-bot opened this issue May 2, 2020 · 0 comments
Assignees
Labels
Closed: Fixed Issue was closed as fixed.

Comments

@sssd-bot
Copy link

sssd-bot commented May 2, 2020

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1961

  • Created at 2013-06-04 20:56:08 by sbose
  • Closed as Fixed
  • Assigned to sbose

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:

  • Issue assigned to sbose
  • Issue set to the milestone: SSSD 1.11 beta
@sssd-bot sssd-bot added the Closed: Fixed Issue was closed as fixed. label May 2, 2020
@sssd-bot sssd-bot closed this as completed May 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Closed: Fixed Issue was closed as fixed.
Projects
None yet
Development

No branches or pull requests

2 participants