-
Notifications
You must be signed in to change notification settings - Fork 900
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
Updating to newer version of net-ldap gem #10635
Conversation
👍 |
To clarify, the fix doesn't cause the |
LGTM other than the comment |
Version 0.14.0 of the gem (actually, starting with 0.13.0) contains a code change that fixes an encoding error (Encoding::UndefinedConversionError) that happens when there are extended characters in a dn. The fix forces utf-8 encoding instead of ASCII-8BIT for objects returned from the directory. See ruby-ldap/ruby-net-ldap#242 https://bugzilla.redhat.com/show_bug.cgi?id=1367600
c893f11
to
895c246
Compare
Checked commit gtanzillo@895c246 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1 |
@jrafanie I fixed the comment in the PR and the commit. Hopefully it's clearer now. Thanks. |
Darga cherry-pick conflict:
|
Version 0.14.0 of the gem (actually, starting with 0.13.0) contains a code change that fixes an encoding error (Encoding::UndefinedConversionError) that happens when there are extended characters in a dn. The fix forces utf-8 encoding instead of ASCII-8BIT for objects returned from the directory. Manually back ported from pull request ManageIQ#10635 due to conflicts
Backported via #10712
|
Updating to newer version of net-ldap gem
Version 0.14.0 of the gem (actually, starting with 0.13.0) contains a code change that fixes an encoding error (Encoding::UndefinedConversionError) that happens when there are extended characters in a dn. The fix forces utf-8 encoding instead of ASCII-8BIT for objects returned from the directory.
See the original PR in the rupy-net-ldap repo.
https://bugzilla.redhat.com/show_bug.cgi?id=1367600
/cc @abellotti @jrafanie