Hi Lars,
thanks for the information.
On 22.04.20 08:52, Lars Liedtke ([email protected]) wrote:
* I created a view on the respective table and login works fine.
* I set SOGoPasswordChangeEnabled = YES; .
OK
* I gave the database user UPDATE rights on the view.
I don't think that this is necessary. At least I didn't have to do it
in my former setups and it works. ;-)
Interesting
Which privileges did you assign to the sogo db user on the sogo database?
In my setups I usually had one database with the accounts for
Postfix/Dovecot and a separate database 'sogo' only for SOGo. The sogo db
user had all privileges on the 'sogo' database, in which I simply created
the necessary view 'sogo_view' to use the respective columns of the account
table in the postfix database.
What I additionally should add is, that I am using two sources of
authentication: AD/LDAP for regular users of our company and SQL for
additional users and aliases (Postfixadmin, Postfix/Dovecot).
Do the regular (AD/LDAP) users see the 'Password' tab and can they use it?
Or isn't it possible for them too?
I tested with the two-source version in a vagrant box, I could of course
let ansible build a box without the AD/LDAP source.
I would test it with only SQL authentication - just to be sure. For such a
test it should be sufficient if you disable the LDAP SOGoUserSources =
(...) in sogo.conf
Regards,
Markus
--
[email protected]
https://inverse.ca/sogo/lists
