Submission from: (NULL) (22.214.171.124)
I'm posting this into the ITS as I didn't get a response on the mailing
after 1 week.
I'm using the latest stable release of openldap, with back-sql and
postgresql as a backend.
I have an sssd which uses this openldap server for ID providing and
A recent update in this sssd changed the filter used to retrieve
groupids of users, which surfaced what seems to be a bug in backsql.
>From my investigation it seems to me that when constructing the search
query, openldap tries to use the UPPER function on every criteria in
the WHERE clause, no matter which type it is. This causes an error in
postgresql, as the gidNumber that is supposed to be filtered is of
I don't recall seeing your message in openldap-technical, which it belongs
to. In any case, there should be a field in ldap_at_mappings that tells
how and when an attribute value needs to be uppercased. However, I can't
check right now whether it works as intended, and back-sql is