headers
pal | 4 Nov 2008 22:16
Picon

sync turba and passwd


I'm checking out Horde to replace my current Squirrelmail installation. What I need to know
first is the possibility to make global address books for all users. In my Squirrelmail
installation I have made a script to collect user ata from passwd file and make a global address
book (text file).

I know Turba uses database backend to store this type of information, but I need to know if
there are any possibility to import such data into the database from a cron job, i.e. to update
the global list once a day?

I guess you will recommend some sort of LDAP to solve this, but LDAP is not an option for my
server at the moment, only passwd.

Any suggestions?

 
--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org
Permalink | Reply | 3 comments |
headers
Jan Schneider | 5 Nov 2008 19:11
Favicon
Gravatar

Re: sync turba and passwd

Zitat von pal <at> hkskole.no:

>
>
>
> I'm checking out Horde to replace my current Squirrelmail  
> installation. What I need to know
> first is the possibility to make global address books for all users.  
> In my Squirrelmail
> installation I have made a script to collect user ata from passwd  
> file and make a global address
> book (text file).
>
> I know Turba uses database backend to store this type of  
> information, but I need to know if
> there are any possibility to import such data into the database from  
> a cron job, i.e. to update
> the global list once a day?
>
> I guess you will recommend some sort of LDAP to solve this, but LDAP  
> is not an option for my
> server at the moment, only passwd.
>
> Any suggestions?

Create a new source driver.

Jan.

--

--
(Continue reading)

Permalink | Reply | 2 comments |
headers
pal | 5 Nov 2008 19:53
Picon

Re: sync turba and passwd

> Zitat von pal <at> hkskole.no:
>
>>
>>
>>
>> I'm checking out Horde to replace my current Squirrelmail
>> installation. What I need to know
>> first is the possibility to make global address books for all users.
>> In my Squirrelmail
>> installation I have made a script to collect user ata from passwd
>> file and make a global address
>> book (text file).
>>
>> I know Turba uses database backend to store this type of
>> information, but I need to know if
>> there are any possibility to import such data into the database from
>> a cron job, i.e. to update
>> the global list once a day?
>>
>> I guess you will recommend some sort of LDAP to solve this, but LDAP
>> is not an option for my
>> server at the moment, only passwd.
>>
>> Any suggestions?
>
> Create a new source driver.
>
> Jan.

Hm, that was not much help for me. What is a source driver? How can I make one? Sounds
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jan Schneider | 6 Nov 2008 00:02
Favicon
Gravatar

Re: sync turba and passwd

Zitat von pal <at> hkskole.no:

>> Zitat von pal <at> hkskole.no:
>>
>>>
>>>
>>>
>>> I'm checking out Horde to replace my current Squirrelmail
>>> installation. What I need to know
>>> first is the possibility to make global address books for all users.
>>> In my Squirrelmail
>>> installation I have made a script to collect user ata from passwd
>>> file and make a global address
>>> book (text file).
>>>
>>> I know Turba uses database backend to store this type of
>>> information, but I need to know if
>>> there are any possibility to import such data into the database from
>>> a cron job, i.e. to update
>>> the global list once a day?
>>>
>>> I guess you will recommend some sort of LDAP to solve this, but LDAP
>>> is not an option for my
>>> server at the moment, only passwd.
>>>
>>> Any suggestions?
>>
>> Create a new source driver.
>>
>> Jan.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Schneider | 8 Nov 2008 18:48
Favicon
Gravatar

Re: [horde] ACL for Turba

Zitat von Bill Day <williamson.day <at> gmail.com>:

> I have been able to configure personal_ldap in sources.php for Turba
> successfully in the past, but for some reason I am having a devil of a time
> writing ACL's for OpenLDAP 2.4 that will give an individual user write
> access to his personal address book.  Although I have spent a fair bit of
> time with the Administrator's Handbook on openldap.org and the Horde Wiki,
> other documentation seems to be sparse and Mr. Google is not providing
> helpful answers.  I have the following questions:
>
> 1) Is there additional documentation that I need to look at?

None that I know of, but I'm not an LDAP guru.

> 2) Is this list the appropriate place to ask for help?  If not, is there a
> more appropriate list?

The Turba list, which I Cc.

> 3) There might also be a possibility that OpenLDAP is not reading all of my
> schema from slapd.conf to the new configurate in cn=config in OpenLDAP 2.4.
> Any advice or suggestions on how to get advice to test this alternate
> hypothesis would be very much appreciated.

Try asking about that on the OpenLDAP mailing list instead.

> 4) Naturally, to the extent this is the appropriate forum, any help would be
> gratefully received.
>
> Thanks,
(Continue reading)

Permalink | Reply | 2 comments |
headers
Bill Day | 8 Nov 2008 20:07
Picon

Re: ACL for Turba

Jan,

Thanks very much for your response.  I finally managed to get the
personal_ldap address book         working (properly, I think).  In
the hope that other Turba users may benefit, I am sharing my
configuration, but more experienced LDAP users may correct
redundancies and identify refinements.  As usual, no warranties, etc.

I am using Ubuntu 8.10, Intrepid Ibex.  Ubuntu has adopted OpenLDAP
2.4, which no longer uses a slapd.conf file.  The most helpful guide I
was able to find is the OpenLDAP Administrator's Guide, at
http://www.openldap.org/doc/admin24/access-control.html#Access%20Control%20via%20Dynamic%20Configuration.

Instead of the slapd.conf file, OpenLDAP's configuration is now
contained in the database itself under cn=config.  After a lot of
trial and error, I was able to figure out that the easiest way for me
to access cn=config was to log into phpldapadmin as
"cn=admin,cn=config" with my master OpenLDAP password.  Most other
tools did not seem to give me access to cn=config, but others'
experience may vary.  After clicking on cn=config in phpldapadmin,
your need to :"display children" and look for the table containing
"olcAccess".

For the configuration that I outlined in my initial post, the
ACL/olcAccess that ultimately worked for me was as follows:

olcAccess: {0}to attrs=userPassword,shadowLastChange by dn="cn=admin,dc=will
iamsonday,dc=local" write by anonymous auth by self write by * none

olcAccess: {1}to dn.regex="[+.]?ou=([^,]+),ou=Personal,ou=Contacts,dc=willia
(Continue reading)

Permalink | Reply | 0 comments |
headers
MailingListe | 13 Nov 2008 13:26
Picon
Favicon

Turba 2.3 without shares and more than one address book

Hello

we are in progress of update Turba 2.0.5 to 2.3. All the tables have  
been extended to the new schema and it basically works. What we have  
trouble with is the following

We have more then one source with different tables and must stick with  
it because some other application using the same database has no idea  
about the e-mail users.
Therefore i have set all sources to "use_shares=false" and set  
permissions with the "admin" user for all sources. This does not work  
(no listing possible) as long as i don't comment out "owner_id" for  
the sources in question.
If i comment out the owner_id unfortunately no owner at all is set  
when adding new contacts.

Is this expected behaviour or have i done something wrong?

Regards

Andreas

--

-- 
All your trash belong to us ;-)  www.spamschlucker.org
To: stephan <at> spamschlucker.org

--
Turba mailing list - Join the hunt: http://horde.org/bounties/#turba
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org
(Continue reading)

Permalink | Reply | 13 comments |
headers
MailingListe | 14 Nov 2008 09:27
Picon
Favicon

Re: Turba 2.3 without shares and more than one address book

Zitat von MailingListe <lst_hoe02 <at> kwsoft.de>:

> Hello
>
> we are in progress of update Turba 2.0.5 to 2.3. All the tables have  
> been extended to the new schema and it basically works. What we have  
> trouble with is the following
>
> We have more then one source with different tables and must stick  
> with it because some other application using the same database has  
> no idea about the e-mail users.
> Therefore i have set all sources to "use_shares=false" and set  
> permissions with the "admin" user for all sources. This does not  
> work (no listing possible) as long as i don't comment out "owner_id"  
> for the sources in question.
> If i comment out the owner_id unfortunately no owner at all is set  
> when adding new contacts.
>
> Is this expected behaviour or have i done something wrong?

I hate to speak with myself but beside some out-of-office replies i  
get no answer so maybe the problem was not clear.

We have Horde 3.3, IMP 4.3, Ingo 1.2.1 and now want to use Turba 2.3  
instead of 2.0.5. We must use 3 tables for our address books as some  
other application using the addresses demand different tables for  
access rights.
To not mix up anything we want to start with "use_shares=false" for  
all sources and set the permissions in the Horde permissions interface  
as the attributes "public" are gone in the new version. With this
(Continue reading)

Permalink | Reply | 12 comments |
headers
LALOT Dominique | 17 Nov 2008 16:22
Picon

localldap source not working

Hello,

I don't know how to get localldap working.

It's not appearing under turba. I found something on the wiki about
permissions:
http://wiki.horde.org/AdminPerms
Turba 2.3 HordeGroupware 3.3
But it didn't help

testDom:~# grep localldap /tmp/horde.log
Nov 14 11:27:39 HORDE [debug] [imp] SQL Query by Prefs_sql::store(): UPDATE
horde_prefs SET pref_value = ? WHERE pref_uid = ? AND pref_name = ? AND
pref_scope = ?, values: localldap  adbf8cddd942d195cf686bcfdeccbc39, lalot,
search_sources, imp [pid 627 on line 244 of
"/var/www/perso/horde-webmail-1.2/lib/Horde/Prefs/sql.php"]
  3 =>
'a:3:{s:6:"source";s:9:"localldap";s:7:"default";b:1;s:4:"name";s:5:"lalot";}',
  3 =>
'a:3:{s:6:"source";s:9:"localldap";s:7:"default";b:1;s:4:"name";s:5:"lalot";}',

testDom:~# grep localldap /var/log/mysql/mysql.log
                     65 Query       SELECT COUNT(*) FROM horde_perms WHERE
perm_name = 'turba:sources:localldap'
                     65 Query       SELECT perm_id, perm_data FROM
horde_perms WHERE perm_name = 'turba:sources:localldap'

What could be the probem. It was working with a fresh new install.

I upgraded from our production environement, running update scripts and then
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Schneider | 17 Nov 2008 16:36
Favicon
Gravatar

Re: Turba 2.3 without shares and more than one address book

Zitat von MailingListe <lst_hoe02 <at> kwsoft.de>:

> Zitat von MailingListe <lst_hoe02 <at> kwsoft.de>:
>
>> Hello
>>
>> we are in progress of update Turba 2.0.5 to 2.3. All the tables  
>> have been extended to the new schema and it basically works. What  
>> we have trouble with is the following
>>
>> We have more then one source with different tables and must stick  
>> with it because some other application using the same database has  
>> no idea about the e-mail users.
>> Therefore i have set all sources to "use_shares=false" and set  
>> permissions with the "admin" user for all sources. This does not  
>> work (no listing possible) as long as i don't comment out  
>> "owner_id" for the sources in question.
>> If i comment out the owner_id unfortunately no owner at all is set  
>> when adding new contacts.
>>
>> Is this expected behaviour or have i done something wrong?
>
> I hate to speak with myself but beside some out-of-office replies i  
> get no answer so maybe the problem was not clear.
>
> We have Horde 3.3, IMP 4.3, Ingo 1.2.1 and now want to use Turba 2.3  
> instead of 2.0.5. We must use 3 tables for our address books as some  
> other application using the addresses demand different tables for  
> access rights.
> To not mix up anything we want to start with "use_shares=false" for
(Continue reading)

Permalink | Reply | 11 comments |

Gmane