Forum

Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.

Difficulté de confi...
 
Notifications
Clear all

Difficulté de configuration authentification Active Directory

4 Posts
2 Users
0 Reactions
4,638 Views
(@coax01)
Posts: 2
New Member
Topic starter
 
[#5399]

English google traduction...

Bonjour, (Hi,)

Despite my research I have not found a solution to my problem on the forum

"exemple"

My domaine controler is in Windows serveur 2012 r2
@ip : 192.168.0.5
Domaine : toto.lan
Nom d'utilisateur : admtoto
Mot de passe : toto01!

Menus : Paramètres>Paramètres globaux>Authentification, i write this informations :

connexion via LDAP : OUI
base dn LDAP : ou=toto_users,dc=toto,dc=lan
serveur LDAP : 192.168.0.5
port LDAP : 389
version LDAP : 3
utilisateur LDAP : cn=admtoto,cn=toto_users,dc=toto,dc=lan
mot de passe : toto01!
filtre pour utilisateurs : uid=%USERNAME%

Before : Paramètres environnementaux>Utilisateurs I add a new user of AD with option "from LDAP" selected.

I'm testing a new connection with new user but fail open session : ** ERROR ** [V7.1.5] cause = ldap_bind(): Unable to bind to server: Invalid credentials

My LDAP parameters are OK with other application : Centreon, GLPI et Libertempo.

Thank you for your help.


 
Posted : 04 Sep 2018 14H51
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

First, with LDAP, search filter should be :
sAMAccountName=%username%

But issue is not here (not yet)
You just cannot connect ot AD serveur.
Credentials is not correct.

I think Ldap User : cn=admtoto,cn=toto_users,dc=toto,dc=lan
does not fit the base dn : ou=toto_users,dc=toto,dc=lan


 
Posted : 05 Sep 2018 1H22
(@coax01)
Posts: 2
New Member
Topic starter
 

Hi,

Thank you for your answer.

I have modified the LDAP user cn to ou value and the filter user uid=%USERNAME% to sAMAccountName (the good syntaxe is juste sAMAccountName or uid=sAMAccountName ?) but i have the same problem.


 
Posted : 05 Sep 2018 11H38
babynus
(@babynus)
Posts: 14957
Main Contributor Admin
 

he good syntaxe is juste sAMAccountName or uid=sAMAccountName ?)

The good syntax is exactly what is written :
sAMAccountName=%USERNAME%

If issue persists, it means you credentials is invalid.
Check user / password.
Also check that projeqtor server has access to LDAP server (sometimes network or LDAP server restricts access)


 
Posted : 06 Sep 2018 12H48
Share:

Scroll to Top