Hi,
We have configured multiple domain with SQL user source, which was
working OK, at least authentication was OK for both domains.
Then, we have manually played with SOGo config, more precisely we have
removed and added back one and then both of following keys:
<key>SOGoEnableDomainBasedUID</key>
<string>YES</string>
<key>SOGoLoginDomains</key>
<array>
<string>a.be</string>
<string>a.com</string>
</array>
Reason, why we played with these section is the following:
According to the config docs, SOGoEnableDomainBasedUID should allow
users to use following login names "usern...@a.be" and "usern...@a.com"
respectively for the second domain. However, that was not the case with
the config above. We had to specify only "username" + to select domain
from dropdown.
So, we decided first to remove SOGoLoginDomains so to remove dropdown
from login page.
It did not give results i.e. only users from first domain could login
with short name. Then, we have put SOGoEnableDomainBasedUID to NO value
and returned SOGoLoginDomains section. Again, only users from the first
domain + selection from dropdown could login.
We realized that users from domain a.com (second one) could not log
anymore. Then we decided to return working (!) SOGo config and the
situation is the same. Users from the second domain could not login anymore.
After returning old working SOGo config, we are getting the following
log entry for the unsuccessful login for user from the second domain:
sogod [5133]: SOGoRootPage Login for user 'u1kronos' might not have
worked - password policy: 65535 grace: -1 expire: -1 bound: 0
Is it possible that SOGo internal DB is damaged now by playing with the
mentioned part of the SOGo config? How we can rebuild SOGo tables if
they are in inconsistent state?
Many thanks,
Igor
--
users@sogo.nu
https://inverse.ca/sogo/lists