| Subject: | Decode values from LDAP when comparing against RT values or updating RT values |
On 01/22/2012 06:24 AM, Ruslan Zakirov via RT wrote:
Show quoted text
> I think from LDAP we get octets, but in RT we should store strings and
> get strings from API calls. To get correct comparison we should
> upgrade data we get from LDAP to perl strings. Google suggests that
> LDAPv3 sends UTF-8, v2 uses some specific format. We can enforce v3 on
> anything that has not ASCII data.
This concurs with what I expected was happening. It's not RT that needs
encoding, it's LDAP that needs decoding.
I do wonder if this problem is present in RT-Authen-ExternalAuth as well.
Thomas