More …
Log files indicate this issue but the displayname is all fine checked and compared with working logins accounts. There are many of this issue.
Some part of the log is overwritten to avoid critical info sharing
“user”:“–”,“app”:“user_ldap”,“method”:“POST”,“url”:“/login”,“message”:“LDAP Login: Could not get user object for DN cn=usersyncissue xxxx xxxxxx,ou=project managers,dc=mycomp,dc=com. Maybe the LDAP entry has no set display name attribute?”,“userAgent”:“Mozilla/5.0 (“version”:“24.0.2.1”}
“user”:”–“,“app”:“no app in context”,“method”:“POST”,“url”:”/login",“message”:“Login failed: usersyncissue (Remote IP: x.x.x.x)”,“userAgent”:“Mozilla/5.0 (“version”:“24.0.2.1”}
“user”:”–“,“app”:“no app in context”,“method”:“POST”,“url”:”/login",“message”:“Login failed: mycomp\usersyncissue (Remote IP: x.x.x.x)”,“userAgent”:“Mozilla/5.0 (“version”:“24.0.2.1”}
{“reqId”:“EtdvxkcIsgIBHNTrBlTe”,“level”:0,“time”:“2024-07-12T20:18:53+04:00”,“remoteAddr”:”“,“user”:”–“,“app”:“user_ldap”,“method”:”“,“url”:”–“,“message”:“No or empty username (admin) for cn=hareesh xxxx xxxxxx,ou=project managers,dc=mycomp,dc=com.”,“userAgent”:”–",“version”:“24.0.2.1”}
why there is admin there ? in Internal Username of ldap expert section
I don’t remember the config it is 2-3 year old and was working fine. last month it started this new user adding issue.
Update : Resolved
In my case Lastpass was filling up that feild with admin and some time back it might have saved it in the form (last month when i review a case with client). After removal of it sync started.
LDAP - EXPERT - Internal Username Attribute - “admin”
LDAP - EXPERT - Internal Username Attribute - “”
In my case ldapExpertUsernameAttr must be empty else it would not work. This happen because in the gui the lastpass add it and some how i clicked continue or something to check something.
Thank you very much every body to helping me!