It looks like you're new here. If you want to get involved, click one of these buttons!
Thane;41635 said:@atreyuTry a rdn that contains uid=%UID% like uid=%UID%,cn=mycn,ou=proxies,dc=my,dc=domain, as it's set now you don't provide a user to bind.If set correctly the diagnostic page will show something like uid=admin,cn=mycn,ou=proxies,dc=my,dc=domain.Note: %UID% is caps sensitive.
$ldap = ldap_connect($vars['ldap_controller'], $vars['ldap_port']);
Thane;41775 said:@jk11for an ad you don't need to use rdn, you can set rdn to off and use the filter in the example:(&(sAMAccountName=%USERNAME%))I've added rdn for those cases, where you can't bind with a filter.
Thane;41995 said:@JK11Did you set the correct suffix?
Thane;42849 said:I'm sorry that i'm replying that late.@JK11try a suffix with like the following: @adserver.domain.comgriffinaaronj could authenticate that way.
velinath;43391 said:edit: Never mind. Had to modify settings-ldap-global.inc.php. The query is pointing to "ldap_ldap_config" table when it should be pointing to "ost_ldap_config" by default, right?
Thane;43489 said:@boolainenThat's as intended, well... in a way. Osticket saves the userdata in the database and retrieves it with every following ticketcreation. You'd get a similar behaviour with the unmodified version. Currently you'd have to manually update every ticket created by the user.I'll think on a way to improve that.