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 ?