ldap over ssl fails

[Anil]

LDAP fails when using it over SSL, port 636. In fact, TLS seems to have problems too - but most of our testing has been with SSL/port 636 option set.

Here is the configuration from the .xml file:

<?xml version="1.0"?>
<group uid="1308802122.3214.17@abc-desktop" name="On LDAP Servers" base_uri="ldap://" readonly="no"><source uid="1308966745.1776.0@abc-desktop" name="Entic.net" uri="ldap://ds1-sjc.entic.net:636/uid=admin,ou=people,o=entic.net??sub?" relative_uri="ds1-sjc.entic.net:636/uid=admin,ou=people,o=entic.net??sub?"><properties><property name="completion" value="true"/><property name="binddn" value="uid=admin,ou=people,o=entic.net"/><property name="auth" value="ldap/simple-binddn"/><property name="remember_password" value="false"/><property name="ssl" value="always"/><property name="limit" value="100"/><property name="default" value="true"/><property name="timeout" value="3"/><property name="can-browse" value="1"/></properties></source></group>

There seems to be a few different bugs open in the recent past related to this. I've tried tinkering with the "ssl" property but without much luck.

We have a few customers who use Evolution with our free LDAP hosting service, http://entic.net/CF (CloudFace) and this is not a problem on the server. The logs on the server appear to show clear-text data over LDAPS.

[Anil (anilj)]

This is with Evolution 2.32.2, Ubuntu 11.04 - the Natty Narwhal.

[Pedro Villavicencio (pedro)]

Linking the report you filed upstream.

[Mathieu Trudel-Lapierre (cyphermox)]

AFAIK this should be working in 2.32 since the release of Natty; so I'll mark this Fix Released (as per the upstream bug).