TimeTrex Time and Attendance

and then binds using the user's LDAP Distinguished Name and then authenticates using the user's DN Excuse this silly redundancy, I typed this from my phone... It should say "...and then binds or authenticates using the user's LDAP Distinguished Name (depending on whether the bind DN and passwo...

When using LDAP for logins, TimeTrex requires the "Bind Attribute" parameter to be set (this should ALWAYS be the user's Distinguished Name, or at least Relative Distinguished Name if the "Base DN" parameter is set, rather than any oddball attribute; the user's CN attribute is th...