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
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.
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1091
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.
Comments
Comment from dpal at 2011-11-17 15:01:48
Low priority even for 1.9.
milestone: NEEDS_TRIAGE => SSSD 1.9.0
priority: major => minor
Comment from dpal at 2012-01-16 16:56:37
Fields changed
blockedby: =>
blocking: =>
milestone: SSSD 1.9.0 => SSSD Deferred
Comment from dpal at 2012-01-19 03:23:58
Fields changed
rhbz: => 0
Comment from jhrozek at 2017-02-24 14:44:02
Metadata Update from @jhrozek:
Comment from pbrezina at 2020-03-24 14:21:46
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.
Comment from pbrezina at 2020-03-24 14:21:48
Metadata Update from @pbrezina:
The text was updated successfully, but these errors were encountered: