General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] Address Book on Postgresql


Chronological Thread 
  • From: Dario Carbone < >
  • To:
  • Cc: Christian Mack < >
  • Subject: Re: [SOGo] Address Book on Postgresql
  • Date: Wed, 06 Feb 2013 12:21:57 +0100

Hi, thanks for the reply.
I've see it on the doc, but don't work for me.

My configurations :

POSTGRESS
i've creted another db called sogo_gab and a table (t_gab) with this columns :

Field name        Type        Array?        Allow nulls?  
    c_uid     varchar(255)     No     No
    c_name     varchar(255)     No     No
    c_password     varchar(255)     No     Yes
    c_cn     varchar(255)     No     Yes
    mail     varchar(255)     No     No
    company     varchar(255)     No     Yes


SOGO :
<dict>
                <key>canAuthenticate</key>
                <string>NO</string>
                <key>displayName</key>
                <string>Primeur GAB</string>
                <key>id</key>
                <string>Primeur_GAB</string>
                <key>isAddressBook</key>
                <string>YES</string>
                <key>type</key>
                <string>sql</string>
                <key>viewURL</key>
                <string>postgresql://sogo:sogo@localhost:5432/sogo_gab/t_gab</string>
</dict>


But dosen't work.
On the log file i saw nothing

Thanks in advice.



Il 06/02/2013 12:03, Christian Mack ha scritto:
" type="cite">
Hello

Am 2013-02-05 12:41, schrieb 
 
 ">
 :
is it possible to use postgresql to have a global address book ?

Sure.
You only have to add another SOGoUserSources of type sql.
You have to set it:
canAuthenticate NO
isAddressBook YES

Example:
  {
    type = sql;
    id = global_addresses
    viewURL = "postgresql://sogo:sogo@127.0.0.1:5432/sogo/sogo_view";
    canAuthenticate = NO;
    isAddressBook = YES;
    displayName = "Addresses for Everyone"
  }


How are the schema to create the DB ?

From the Documentation:

viewURL database URL of the view used by SOGo. The view expects
       columns to be present. Required columns are :
      • c_uid : will be used for authentication – it's a username
        or 
 
 ">
 
      • c_name : will be used to uniquely identify entries – which
        can be identical to c_uid
      • c_password : password of the user, plain text, crypt, md5
        or sha encoded
      • c_cn : the user's common name
      • mail : the user's email address
      Other columns can exist and will actually be mapped
      automatically if they have the same name as popular LDAP
      attributes (such as givenName, sn, department, title,
      telephoneNumber, etc.)

Mind, that view is here used as synonym for table too.


Kind regards,
Christian Mack


--

Carbone Dario                                                                
Primeur Customer Services S.r.l. 
EMAIL: ">
URL: 
http://www.primeur.com
Mobile: +39 3488960584
image003.jpg




Archive powered by MHonArc 2.6.18.

Top of page