Learn more about these different git repos.
Other Git URLs
In the "ID MAPPING" section of the manpage, the ldap_idmap_range_size should have a mention that the value should be atleast the user's corresponding RID on the AD Server.
e.g. for a user with objectSid=S-1-5-21-2153326666-2176343378-3404031434-1107, ldap_idmap_range_size should be atleast 1107. Lookups/enumeration for the user will not work if a value less than that is mentioned.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=845255
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=845255 845255]
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
proposed_priority: => Important
Cleaning the 1.10 milestones before putting tickets into it.
milestone: SSSD 1.10 beta => Temp milestone
Moving planned features and bug fixes into the 1.10 bucket.
milestone: Temp milestone => SSSD 1.10.0
milestone: SSSD 1.10.0 => Temp milestone
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: Temp milestone => SSSD 1.10 beta
priority: major => minor
priority: minor => major
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
design_review: => 0
milestone: SSSD 1.13 beta => Interim Bucket
priority: major => critical
review: => 0
milestone: Interim Bucket => SSSD 1.12 beta
owner: somebody => preichl
patch: 0 => 1
I'm not sure why this ticket wasn't closed, sorry. Closing now.
resolution: => fixed
status: new => closed
Metadata Update from @kaushikub:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.12 beta
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:
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.
to comment on this ticket.