I have also had this issue with Verisign certificates. I managed to at
least test how it should work by using a Thawte server certificate which we
had running in about 15 minutes. I never did figure out what the issue was,
though I suspect the people that originally requested the certificate did it
for a different directory server instance ...
Best of luck
"Rob Reid" <[EMAIL PROTECTED]> wrote in message
986gl9$[EMAIL PROTECTED]">news:986gl9$[EMAIL PROTECTED]...
>
> So, I've installed and trusted my Verisign certificate, made all of the
> neccessary configuration changes required and have gotten the slapd server
> to restart successfully on port 389 and 636.
>
> BUT, the darned server will not respond to any request on the secure port:
>
> Here's what the logs show...
>
> [07/Mar/2001:14:58:52 -0800] conn=3 fd=32 slot=32 SSL connection from
> 127.0.0.1 to 127.0.0.1
> [07/Mar/2001:14:58:52 -0800] conn=3 op=-1 fd=32 closed error -12199
> (unknown) - B1
>
>
> Is it me, or is the iPlanet Admin Console one of the worst applications
ever
> released?
> I've configured SSL for many a webserver and I've never experienced the
> level of fustration that I have with this iPlanet product.
>
> Heck, is there anyway to configure ssl without using the lousy admin
> console? That would sure be nice!!!!!
>
> Rob Reid
> [EMAIL PROTECTED]
>
>
>
