Learn more about these different git repos.
Other Git URLs
This approach was suggested by Simo on the sssd-devel mailing list - https://fedorahosted.org/pipermail/sssd-devel/2011-November/007530.html
The proxy backend could be plugged into virtually any kind of database. That database, unline LDAP, is not guaranteed to use UTF-8, but it can use some random code page.
SSSD could pass around usernames/filters as byte arrays instead of UTF-8 strings to avoid DBus choking on invalid UTF-8 strings.
Low priority even for 1.9.
milestone: NEEDS_TRIAGE => SSSD 1.9.0 priority: major => minor
Fields changed
blockedby: => blocking: => milestone: SSSD 1.9.0 => SSSD Deferred
rhbz: => 0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Patches welcome
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/2133
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.