The cert is self-signed, but by different CA's (each server has it's own CA).
You know what? I took your hint and signed a new server cert using
the "working" ldap server's CA and voila, it started working. Thank
you so much! I've been scratching my head over this one for days
David
On Thu,
On 07/19/2012 10:28 AM, Gary Algier wrote:
Hi,
I am in the process of migrating from Sun's DS 5.2 to DS 389 and I
have compared the schemata. I see some differences and I wonder as to
the best way to handle them. In general is it better to change the
389 schema and then always have to "fix"
Hi,
I am in the process of migrating from Sun's DS 5.2 to DS 389 and I have
compared the schemata. I see some differences and I wonder as to the best way
to handle them. In general is it better to change the 389 schema and then
always have to "fix" it with each new release or change my Sun c
Hi,
what kind of certificate do you use, selfsigned? Are the certificates signed by
the same CA?
Am 18.07.12, schrieb David Nguyen :
> Hi all,
>
> I have a strange one. My current setup is working perfectly. client1
> is able to connect to ldap-server1 via SSL and everything is working
> c
