2nd domain configuration ignored in a multi domain setup

[Eld]

Hi !

I upgraded two distinct instances of egroupware 1.8 to 17.1 and merged them in a multi domain configuration.

So header.inc.php describes :

• domain1 with db1
• domain2 with db2
  (both domains where previously described as ‘default’ on their vms)

Both db1 and db2 include their own egw_config table with ldap contexts pointing to ou=domain1,dc=example,dc=com and ou=domain2,dc=example,dc=com respectively

Databases updates went fine and the first egw domain is up and running. But authentication on domain2 fails and the LDAP server records searches on the wrong context !

I triple checked the configuration values for domain2 : the ldap contexts are correct, they appear correctly both in the database and in the setup configuration page. Result is the same wether we try to connect with username @domain2 or via the domain selection box : egroupware seems to follow the configuration of domain1 only.

Is there a way to figure out what happens during the login process, and what are the configuration variables states ?

Regards,

[RalfBecker]

Hi Eid,

in a multi-domain config you either want to:

• use different domain names / vhosts matching what you use in our header or
• enable the domain-select-box in the header, as a means for your users to manually switch between the domains

Recommended is always the first possibility with two different domain names automatically selecting the correct database and therefore LDAP context.

Ralf

[Eld]

Hi Ralf,

Thank you for your answer!

We wanted a single vhost so that it would make the clients configuration easier. Both egroupware domains are associated to the same URL. The domain-select-box is enabled in the header and is displayed on the login page. But we end up with a request on the first domain LDAP branch whatever the domain selected.

If I ask the account_migration.php in the setup of the second domain, the accounts are found in the right LDAP context, so the values in the egw_config are correct. So the login is probably done on the wrong database but I can’t understand why…

Any clue?

Laurent