LDAP auth error: can't decode byte 0xc3

[arturbrandysonwelo]

Is the issue already present in https://github.com/cloudera/hue/issues or discussed in the forum https://discourse.gethue.com?
Yes but it is closed (#2250).

Describe the bug:
In HUE 4.10.0 some LDAP users are not able to login anymore.

[14/Jun/2021 08:46:34 +0000] backend INFO Augmenting users with class: <class 'desktop.auth.backend.DefaultUserAugmentor'>
[14/Jun/2021 08:46:34 +0000] forms ERROR LDAP auth error: 'ascii' codec can't decode byte 0xc3 in position 18: ordinal not in range(128)

This blocks migration to 4.10 if connected to LDAP

Steps to reproduce it?
Connect to LDAP directory with users containing special characters in their names (some polish letters: ł ó ą ...)

Hue version or source? (e.g. open source 4.5, CDH 5.16, CDP 1.0...). System info (e.g. OS, Browser...).
open source 4.10 - OS: Windows 10; Browsers: Firefox

Connected with issue: #2250

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity and is not "roadmap" labeled or part of any milestone. Remove stale label or comment or this will be closed in 5 days.

[gzhukov]

Hi, I can confirm that hue since v4.8.0 has some bug with at least cyrillic ldap-groups:
[24/Oct/2021 00:29:41 +0300] forms ERROR LDAP auth error: 'ascii' codec can't decode byte 0xd0 in position 3: ordinal not in range(128)

[gzhukov]

Hi, simple patch for this issue is here: #2622
Tested with hue v4.10.0

[gzhukov]

Also looks like sometimes we gets binary string in "username_pattern":
Pushed fix to the same branch.

Also if you use gethue docker image with non-ascii locale, you should rebuild gethue image with additional steps:
`
FROM myhue:4.10.0
RUN apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y locales && apt-get clean
RUN sed -i '/en_US.UTF-8/s/^# //g' /etc/locale.gen && locale-gen
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8

`
It prevents logger errors for non-ascii symbols.

[Harshg999]

Merged PR: #2622

[Harshg999]

@arturbrandysonwelo - Thanks for reporting this issue!
@gzhukov - The fix has been merged. Thanks for your contribution!

It has been committed in the master branch, it will be part of the 4.11 release.