AD-LDAP login with ProjeQtor 5.0.0

Hi,

I'm testing this web application (lastest 5.0.0 RC version) and it seems to be exactly what I need. But I'm facing an issue with LDAP authentication.
I've an Active Directory LDAP and i've this error in log file when attemping to login :

2015-06-19 09:05:51.492 ===== TRACE ===== Login error for user 'myusername'

I set this as parameters :
connection with LDAP user :
LDAP base dn : dc=domain,dc=local
LDAP host : [IP of primary DC]
LDAP port : 389
LDAP version : 3
LDAP user : cn=[administrator name],cn=Users,dc=domain,dc=local
LDAP password : [administrator password]
LDAP user filter : sAMAccountName=%username%

These settings are working with other Web application that uses LDAP authentication (like GLPI). The log file does not tell me what's wrong except a login error but i'm sure the login typed in is correct and matches sAMAccountName field.

Any help will be greatly appreciated.

Regards.

Eric

Additional point : If I change the LDAP user filter with something wrong, log file shows

2015-06-19 13:39:47.942 ***** ERROR ***** cause = ldap_search(): Search: Bad search filter

So, in my mind, it seems my initial user filter is OK.

Hi and thanks for your quick reply.

AD uses the standard LDAP port 389 and authentification works fine with this setting for other web app like GLPI. I tried secured port 626 but without success. In GLPI's case, I use successfully this connexion filter :

(&(objectClass=user)(objectCategory=person))

I tried with different syntax like

(&(objectClass=user)(objectCategory=person))=%username%

But it doesn't work with ProjeQtor and generates this error in log file :

***** ERROR ***** cause = ldap_search(): Search: Bad search filter

The only way to not have a bad search filter error is to use

sAMAccountName=%username%

but then I have

Login error for user 'myusername'

.

About the second solution, I'm using Windows 2008r2 AD controler and not 2012r2. But anyway, I checked the LDAP connexion string as explained and all is OK. In my AD, the connexion username is set in "sAMAccountName" key. Tried other filled keys like CN (gives "FirstName LastName"), displayName (gives "LastName FirstName") or Name (gives "FirstName LastName"), without any success and always the same

Login error for user 'myusername'

.

This is going to drive me crazy...

I got it !!!

It was simply a case sensitive behavior ! In LDAP user filter, I used the bad :

sAMAccountName=%username%

But the good one is :

sAMAccountName=%USERNAME%

!!!

Seems this solution is only available for Projeqtor v5.0. Maybe the case of %username% does not matter in version 4.x ?