Hi,
you have to create an authentication table (sogo_auth).
My MySQL table looks like this:
c_uid varchar(50) latin1_swedish_ci
c_name varchar(50) latin1_swedish_ci
c_password varchar(50) latin1_swedish_ci
c_cn varchar(101) latin1_swedish_ci
mail varchar(68) latin1_swedish_ci
Example:
c_uid = john.doe
c_name = john.doe
c_password = xxx
c_cn = John Doe
mail = [email protected]
You don't have to manage two user databases. I created a view (called
sogo_auth) to point the SOGo field names to an existing user database.
kind regards,
Christian
__________________________________________
Christian Reischl
Fraunhofer Institut für
Verfahrenstechnik und Verpackung
Giggenhauser Str. 35
85354 Freising
Telefon: 08161 491-704
mailto:[email protected]
http://www.ivv.fraunhofer.de
Peter Peltonen schrieb:
I have done my first SOGo 1.3.8b installation on a CentOS6 server. My
aim is to use SQL and not LDAP.
I have a few basic questions about SQL authentication that were not
clear when reading installation guide:
- I have created a PostgreSQL database and a user as instructed, but
in the guide there was nothing about the actual data that should go in
the DB? Do I need to create some tables as well?
- "Managing User Accounts" talked about LDAP only. How do I create an
admin user with SQL?
- Is this the way SOGo is intended to be used:
1. With SOGo web interface, after creating an admin user I create a
normal user
2. I specify the IMAP credentials for this user in SOGo with the
admin user account
3. Now the user can log into SOGo and see his email + new shared calendar
If so, this means that I need to manage two user databases, in the
IMAP server and in SOGo? And if a user changes his/her IMAP password
by not using SOGo but for e.g. external webmail, I am in trouble?
I have a feeling that I have not yet grasped all the principles of
this software package and I am missing some points here :)
Best regards,
Peter
--
[email protected]
https://inverse.ca/sogo/lists
