SSSD / sssd

#2188 automatically assign new slices for any AD domain
Closed: Fixed Opened by simo.

Closed: Fixed
Reopen Issue

When a domain RID grows beyond the slice size it may make sense to have sssd allocate a new slice automatically instead of relying on the admin to find the fault and increase the slice size.
this also helps if there are large gaps in the RID space so that smaller slices are used.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => todo

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1059972 (RHEL RFE)

rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1059972 1059972]

Fields changed

mark: => 0

Makes sense, but perhaps we won't have the time in 1.13.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

I ran into two cases that hit the hardcoded range size this week. We might want to reconsider. The cheap way would be to log more prominently.

milestone: SSSD 1.14 beta => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 backlog

Related FreeIPA ticket - https://fedorahosted.org/freeipa/ticket/4527

Fields changed

priority: major => critical
sensitive: => 0

The IPA provider of SSSD always get the idranges from the server, see FreeIPA ticket.

For the AD provider we can add a scheme similar to the one used by the samba autorid module. If there is the RID outside of the rage detected calculate the integer part of RID/range_size and append this to the domain name as domain_name#N. Then take the hash value of domain_name#N to find a new slices for the RID.

Fields changed

owner: somebody => preichl

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1268902 (Red Hat Enterprise Linux 6)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=1059972 1059972] => [https://bugzilla.redhat.com/show_bug.cgi?id=1059972 1059972], [https://bugzilla.redhat.com/show_bug.cgi?id=1268902 1268902]

This ticket shouldn't be in the backlog but 1.13.4

milestone: SSSD 1.13 backlog => SSSD 1.13.4

Fields changed

patch: 0 => 1

master:

  • 8babbeee01e67893af4828ddfc922ecac0be4197
  • c3cdd6a644a870531092e4378cbcd1a428ff514c

sssd-1-13:

  • 4d7877584e41c4494624f06144b3716db8979b5f
  • 9fdc9707defb8110a1f8ebf7f7cf414b80ee7f15

resolution: => fixed
status: new => closed

master:

  • 4f3a996561445ba82c854bb2b674f975f596e884

sssd-1-13:

  • 999af61d6a55bf816d86dbfc94214383436b18d3

Fields changed

design: => https://fedorahosted.org/sssd/wiki/DesignDocs/IdmapAutoAssignNewSlices

Metadata Update from @simo:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.13.4

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3230

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
Low
defect
SSSD
1.11.3
https://bugzilla.redhat.com/show_bug.cgi?id=1059972, https://bugzilla.redhat.com/show_bug.cgi?id=1268902
https://fedorahosted.org/sssd/wiki/DesignDocs/IdmapAutoAssignNewSlices
0
1
0
0
0
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.