|
Hello , I hope this is the right point for my problem: we have a 2.4.40 slapd running on Debian Jessie with inetOrgPerson entries that have (indexed) numerical uid values. No problems if the user login on our web app (moodle) but some users get input mistakes and use superscripted first letter which also works. Here an example: uid=1228849 and uid=¹228849 works also. If I check the debug output for the superscripted version I got: May 24 09:44:23 rldapd slapd[600]: begin get_filter May 24 09:44:23 rldapd slapd[600]: EQUALITY May 24 09:44:23 rldapd slapd[600]: end get_filter 0 May 24 09:44:23 rldapd slapd[600]: filter: (uid=1228849) May 24 09:44:23 rldapd slapd[600]: attrs:If I trace the network traffic data there is a difference between the queries 0x0090: 0375 6964 0407 3132 3238 3834 3930 00 .uid..12288490. 0x0090: 0375 6964 0408 c2b9 3232 3838 3439 3000 .uid....2288490. The command line tool "ldapsearch" do the same. So for the web app the superscripted version is a different user and for slapd it is not. Why slapd is interpreted the superscripted 1 as 1? Is this a bug or must check the input before it is send to slapd? Thanks for any help. Best regards Rene -- |
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature