Re: [Evolution] Evo 1.2 & LDAP with MS Exchange Server

[Chris Toshok <toshok ximian com>]

On Tue, 2002-11-19 at 14:12, Cormac Long wrote:
> Does anyone have evo 1.2 working with MS Exchange LDAP server?.. if so
> can you provide details of the configuration.. bind, scope etc
>
> I've monitored evo and gq using Ethereal.. 
>
> Results from using gq (which works)
> firstly, it binds but with simple authentication and dn and password
> set to NULL
>
> Lightweight Directory Access Protocol
>     Message: Id=1  Bind Request
>         Message Length: 7
>         Version: 2
>         DN: (null)
>         Auth Type: Simple (0x00)
>         Password: (null)
>
> Evo won't allow you to set dn and password to NULL.. you either don't
> bind at all or use non-null email or dn binding... both of which fail
> on my LDAP server.

Hmm, this is because evolution assumes (perhaps incorrectly) that
connections start up in anonymous state.  This assumption is valid for
openldap servers, lemme check the rfc...

Can't find anything about the initial state of a connection, so while it
might be a faulty assumption, in this case it looks like the scope
(below) is the issue.

> Then for the search, gq does the following:
> Lightweight Directory Access Protocol
>     Message: Id=2  Search Request
>         Message Length: 33
>         Base DN: (null)
>         Scope: Subtree (0x02)
>         Dereference: Never (0x00)
>         Size Limit: 0
>         Time Limit: 0
>         Attributes Only: False
>         Filter: (cn=*long*)
>
> Evo which can't do NULL binds, goes straight for the search and does
> the following:
> Lightweight Directory Access Protocol
>     Message: Id=7  Search Request
>         Message Length: 53
>         Base DN: (null)
>         Scope: Base (0x00)
>         Dereference: Never (0x00)
>         Size Limit: 100
>         Time Limit: 0
>         Attributes Only: False
>         Filter: (|(cn=*long*)(sn=*long*))
>
> The search string given to gq was "long" and because it was configured
> for searching cn with a "contains" rule, it added the * before and
> after the string.
>
> The evo search fails with just "long" and "*long*" when I tried to
> emulate the gq search.
>
> All I can assume is that it fails because I can't set the scope to be
> subtree (evo only allows base and one to be selected) or it has
> something to do with the inability to bind with dn=NULL,
> password=NULL.

Hmm, in fact evolution 1.2 should only use one and sub (for user
queries).  It's a bug if it's generating anything with base.

> When I was using evo back on the 1.0.X days, I had LDAP working.. its
> only since I moved to evo 1.2 that it doesn't work.

Was this ldap sever added with 1.0.8 or 1.2?  If it was added with 1.0.8
can you try and enter the settings again with a differently named server
(in 1.2) and see if it works?  Also, could you paste the <contactserver>
block for the server that's not working (deleting any sensitive
information if you want) into a reply?

Chris