Re: horde/turba anonymous bind

Zitat von Alain Abbas <alain.abbas <at> libertech.fr>:

> Hello
> Turba the address book of horde bind in anonymous mode to search in the
> global address book
> that forbid acls for certains groups or certains organizationalUnit and
> doesn t allow us
> to make acl by users
>
> How to make Turba to bind with the dn and the password of the user ?

You can use

$mail = Auth::getAuth();
$pass = Auth::getCredential('password');

in

/kolab/var/kolab/www/client/turba/config/sources.php

You will need to add some LDAP command to map the $mail to the LDAP DN  
of the user.

The DN and the $pass are required as

                 'bind_dn' => '',
                 'bind_password' => '',

in $cfgSources['kolab_global']

Re: horde/turba anonymous bind

Hi,

attached is a config for adresses in ldap, both private and public with pass.
It stores (and expectes) the users addresbooks under
ou=addr,uid=username,ou=domain,ou=com

Works fine for me.

regards
Alex

-- 
Dipl.-Inform. Alexander Gran, MBA
Neusser Straße 388  50733 Köln  Germany
M: +49(0)163/5598933  Encrypted Mails welcome.
Steuernummer 217/5094/3247 Ust-IdNr.: DE259069010
PGP-Key at http://www.grans.eu/misc/pgpkey.asc | Key-ID: 0x6D7DD291

--

-- 

Visit ModuleWorks at:

IMTS 2010, 13.09 - 18.09 - Chicago, East Building Booth E4120
Euromold 2010, 01.12 - 04.12 - Frankfurt, Hall 11.0 E102

Dipl. Inform. Alexander Gran, MBA
alexg <at> moduleworks.com
http://www.moduleworks.com
SkypeID: mw_alexg
M: +49(0)163/5598933  

Re: what are the correct magic_quotes settings in Kolab

Zitat von Gavin McCullagh <gavin.mccullagh <at> gcd.ie>:

> Hi,
>
> here in Ireland, the apostrophe appears very commonly in surnames, such as
> "O'Reilly" and "O'Regan".  The O' is an anglicised version of Ó which means
> "of" (as in born of) in Irish.
>
> We're finding putting apostrophes in names is causing problems in our kolab
> v2.2.4 install.  I'm not sure if these are little code bugs or if perhaps
> PHP has the wrong magic_quotes settings.
>
> phpinfo() shows these three entries:
>
>           Directive             Local Value		       Master Value
> magic_quotes_gpc                On                                 On
> magic_quotes_runtime            Off                                Off
> magic_quotes_sybase             Off                                Off
>
> Is that the correct config for Kolab?  Is there a prescribed config?  There
> doesn't seem to be any mention of quotes in php.ini or apache-php.ini.

Hm, that is weird. Are you running on Kolab Server 2.2.4?

This was touched in 2.2.4 and HEAD:

http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/php.ini.template.in.diff?r1=1.8&r2=1.9
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/php.ini.template.in.diff?r1=1.7&r2=1.7.2.1

See also the associated issues from the log commit messages:

Re: anyone know how to bind kolab2.2.4 to a specific network adapter?

Zitat von Gavin McCullagh <gavin.mccullagh <at> gcd.ie>:

> Hi,
>
> On Mon, 30 Aug 2010, Shannon Kuchler wrote:
>
>> running kolab 2.2.4 on a server with more than one network adapter
>> I need to know how to make sure kolab binds to eth1 every time the system is
>> rebooted
>> I need eth0 for another instance on Apache
>
> When you say kolab, I gather you mean just the apache component.
>
> If you look in the apache template config,
> /kolab/etc/kolab/templates/httpd.conf.template you should see:
>
>  <at>  <at>  <at> if bind_any <at>  <at>  <at> 
> Listen 80
> Listen 443
>  <at>  <at>  <at> else <at>  <at>  <at> 
> Listen  <at>  <at>  <at> bind_addr <at>  <at>  <at> :80
> Listen  <at>  <at>  <at> bind_addr <at>  <at>  <at> :443
>  <at>  <at>  <at> endif <at>  <at>  <at> 
>
> so to bind to a specific address you need bind_any set to false and
> bind_addr set to the IP of the interface you want bound to.  You can set
> these in /kolab/etc/kolab/kolab.globals

The settings should go into /kolab/etc/kolab/kolab.conf as  
kolab.globals is meant to provide the default settings which should  

Re: anyone know how to bind kolab2.2.4 to a specific network adapter?

On Wed, 01 Sep 2010, Gunnar Wrobel wrote:

> > so to bind to a specific address you need bind_any set to false and
> > bind_addr set to the IP of the interface you want bound to.  You can set
> > these in /kolab/etc/kolab/kolab.globals
> 
> The settings should go into /kolab/etc/kolab/kolab.conf as  
> kolab.globals is meant to provide the default settings which should  
> not be touched. I added a note concerning that to CVS HEAD a while ago  
> but that will only be part of Kolab Server 2.3.

Ah.  Oops, thanks and sorry for the misinformation.

Gavin

Re: what are the correct magic_quotes settings in Kolab

Hi,

On Wed, 01 Sep 2010, Gunnar Wrobel wrote:

> Hm, that is weird. Are you running on Kolab Server 2.2.4?

Yes.  Can I ask if someone here can reproduce this, just so I know it's not
a mistake I've made in config somewhere?  Just try and add someone with the
surname O'Reilly.

What I actually observe is:

1. Create a user with surname with ' in it succeeds without error in web
   admin.  I created "Gav O'Really" for testing just now.
2. Find that user in the list.  You'll notice it displays as 
	O\'Really, Gav
3. Click on modify on that user.  That results in this error:
	LDAP Error: No such dn: cn=Gav O\\5C\'Really,dc=....: Invalid DN syntax
4. A similar error in apache/php/php-errors.log:
 	[02-Sep-2010 08:36:47] PHP Warning:  ldap_read() [<a
href='function.ldap-read'>function.ldap-read</a>]: Search: Invalid DN syntax in
/kolab/var/kolab/php/admin/include/ldap.class.php on line 187
5. If I look at the ldap database using ldapvi or slapcat I see escape
   characters in cn and sn:
	cn=Gav O\\5C'Really,dc=.....
	objectClass: top
	objectClass: inetOrgPerson
	objectClass: kolabInetOrgPerson
	sn: O\'Really
	cn: Gav O\'Really

Re: what are the correct magic_quotes settings in Kolab

On Thu, 02 Sep 2010, Gavin McCullagh wrote:

> I'm creating a new issue now.

https://issues.kolab.org/issue4526

Re: what are the correct magic_quotes settings in Kolab

On Wed, 01 Sep 2010, Gunnar Wrobel wrote:

> Hm, that is weird. Are you running on Kolab Server 2.2.4?
> 
> This was touched in 2.2.4 and HEAD:
> 
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/php.ini.template.in.diff?r1=1.8&r2=1.9
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/php.ini.template.in.diff?r1=1.7&r2=1.7.2.1

Adding 
	magic_quotes_gpc off

seems to sort this out.  For some reason this isn't in the php.ini.template
config that came with 2.2.4.

Gavin

Re: what are the correct magic_quotes settings in Kolab

Hi Gavin,

Zitat von Gavin McCullagh <gavin.mccullagh <at> gcd.ie>:

> On Wed, 01 Sep 2010, Gunnar Wrobel wrote:
>
>> Hm, that is weird. Are you running on Kolab Server 2.2.4?
>>
>> This was touched in 2.2.4 and HEAD:
>>
>> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/php.ini.template.in.diff?r1=1.8&r2=1.9
>> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/kolabd/kolabd/templates/php.ini.template.in.diff?r1=1.7&r2=1.7.2.1
>
> Adding
> 	magic_quotes_gpc off
>
> seems to sort this out.  For some reason this isn't in the php.ini.template
> config that came with 2.2.4.

I just looked at a fresh 2.2.4 server and verified that  
/kolab/etc/kolab/templates/php.ini.template contains

magic_quotes_gpc   = 0

This seems to be something that only happened on your side. Was this a  
server you upgraded? Did it contain prior modifications to the  
php.ini.template?

Cheers,

Fwd: Re: Meeting requests are ignored

Guess this was meant for the mailing list.

--
Gunnar Wrobel
Developer, Kolab Systems AG

e: wrobel <at> kolabsys.com
t: +49 700 6245 0000
w: http://www.kolabsys.com

pgp: 9703 43BE

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

From: schmerold2 <at> gmail.com <schmerold2 <at> gmail.com>
Subject: Re: Meeting requests are ignored
Date: 2010-09-01 19:11:36 GMT

It is Kolab 2.2.2, I see no obvious errors reported in 
/kolab/var/kolab-filter/log files.

I suspect Kolab is sending meeting requests somewhere, however I have 
not idea where to begin looking for the destination, or more