LDAP Doesn't escape commas in DN when binding user

[casonjase]

Bug Description

When using LDAP with Windows AD, It appears that if a CN contains a comma it will fail to bind the user as the DN will contain the comma as well. Even though the escape is accounted for in the DN itself. All of our CN's contain commas. You get error "Verification failed, please confirm that the username and password are correct." until the comma is removed.

Example

User Doe, John

DN CN=Doe, John,OU=IT,OU=Employees,DC=company,DC=com

Thank you :)

How to Reproduce

Update a users Common Name in AD to something like Doe, Joe and try and login. Login will Fail unless the comma is removed

Expected Behavior

Should be able to login if the CN contains a comma or not.

Operating system(s) on local (controlling) side and remote (controlled) side

Windows 11

RustDesk Version(s) on local (controlling) side and remote (controlled) side

RustDesk Server Pro 1.6.3

Screenshots

Additional Context

No response

[fufesou]

I'll fix it.