FreeIPA 4.6.1 cannot bind on 636 but can connect on port.

[Matt .]

Hi Guys,

I have some strange issue where FreeIPA 4.6.1 accepts telnet connections on port 636 but no bind. Both are successful on 389.

This didn't happen on 4.5.4.

Any idea ?

Thanks,

Matt

[Matt .]

No-one a clue about this ?

[Natxo Asenjo]

hi,

could you try using ldapsearch with the -d 10 switch? That shoud give you
plenty of debugging info.

--
Groeten,
natxo

[Matt .]

Hi,

I can do!

Can it be that the certificate, self signed, is more of a security issue now and that causes the problem ? In the past I was able to use a selfsigned one for internal tests.

Cheers,

Matt

[Rob Crittenden]

Matt . via FreeIPA-users wrote:
> Hi,
>
> I can do!
>
> Can it be that the certificate, self signed, is more of a security issue now and that causes the problem ? In the past I was able to use a selfsigned one for internal tests.

As I asked in IRC you need to provide a GOOD description of what you are
doing, what output you are seeing and what you expect to see. Including
full command-line, stdout, etc. And I guess particularly where these
certs came from, how you generated them, etc.

rob