Authentication, multiple ldap servers

[Franck17000]

Well, well well...
I'd like to obtain the same functionalities than PLA 1 : Whe have 10 LDAP servers who have 3 or 4 branch each and we are able to log on each branch with different credentials.

As I can see, PLA 2, at this time, works only with 1 server, and you should configure log informations (not only servers informations).

I mapped the config directory to a local folder and tried to add servers into "ldap.php" file. Unfortunatly, it manager only the default server, and crash with "no default server'.

As well, login screen for non anonymous usage (...and embeded login, then) doesn't work at all.

Is anyone :

• Had anyone sucessfully configure PLA2 without credentials wrote in config file ?
• Had anyone use PLA2 with more than 1 LDAP server ?

I was hopping a lot from this app because we're using it often like it... Thank you, if I ask the impossible (..or "not yet"), I'd like to avoir wasting time...

Thank you too to trie to give life to this application ;-)

[leenooks]

Had anyone sucessfully configure PLA2 without credentials wrote in config file ?

Yes, start the container with

LDAP_USERNAME=
LDAP_PASSWORD=

(Because the defaults for those variables have a value - see config/ldap.php, which I may remove in the next release.)

Had anyone use PLA2 with more than 1 LDAP server ?

When I started with PLA v2, I considered supporting mulitple servers (like I did in v1) - but I actually didnt think anybody would be using multiple unique servers in an organisation. So no, PLA v2 hasnt been designed to work with more than 1 server.

You could run 10 instances of PLA.

Why have you got 10 LDAP servers?

[Franck17000]

Yes, start the container with

LDAP_USERNAME=
LDAP_PASSWORD=

Ok I'm gonna try this !

You could run 10 instances of PLA.

Why have you got 10 LDAP servers?

OK. We have 1 master and 2 replicated slaves. Of course the main work is done on master but we check sometime replication of ldap entries. This is x3 again because we have production, qualifiying and test environments. Then I can understand it's a specific case !

Thank you again, I'll keep you informed about the fight vs conf files 🤣

[Franck17000]

Yep.
So I can now login with LDAP_ALLOW_GUEST=false but I should define an account (LDAP_USERNAME / LDAP_PASSWORD) to allow PLA2 to read server before.

To self-answer this topic :

I fought a lot with login.. Red "Whoops..." at logon :

• First, I didn't read rootdn account is not allowed. OK...
• Second, I didn't redefine LDAP_LOGIN_OBJECTCLASS='inetOrgPerson' (default posix account..)

It's really a shame for us if we should run an instance for each server, and each branch... 10 servers, and at least 6 branch on each.

Stay with an another error, I'll post another specific topic, pleasure of giving, joy of receiving 🎁

If it helps, my running env. file :

APP_KEY='base64:+MeOL+TDpQXh7****************9UeAjdsjtIjarON3Y='
#DO NOT SET OR CRASH :  APP_URL='https://pla-test.mydomain'
APP_DEBUG=true
APP_TIMEZONE='Europe/Paris'
LDAP_HOST='ldapmaster.mydomain'  # MANDATORY OR CRASH
LDAP_ALLOW_GUEST=false
LDAP_LOGIN_ATTR='dn'
LDAP_LOGIN_OBJECTCLASS='inetOrgPerson' # VERY IMPORTANT FORM ME
LDAP_BASE_DN='o=firstbranch'
LDAP_NAME='TEST-MASTER-BRANCH1'
LDAP_PORT='389'
LDAP_USERNAME='cn=pla2,ou=administrators,o=firstbranch' #Just the rights to read
#LDAP_USERNAME=
LDAP_PASSWORD='Wyhzardfn234dfsdfdVX' # ..Not the real passwd :-p
#LDAP_PASSWORD=
LDAP_ALERT_ROOTDN=false
LDAP_CACHE=false
LDAP_SSL=false
LDAP_TLS=false
LDAP_SASL=false
#LDAP_CONNECTION='ldap'
LDAP_TIMEOUT=90
LOG_LEVEL=debug
LDAP_LOGIN_ATTR_DESC='Entez le dn'