You have to enable SSL at the server and at the client app. You fail at
the
"SSL Handshake" phase.
gls
Garban
Fujian Yang wrote:
> Hello,
>
> I'm using SSL to connect a client(written with JSSE1.0.2) and a iPlanet
> web server 4.1. And I want to do both server and client authentication.
>
> For the server authentication I got a trial server certificate from
> Verisign, it works fine.
>
> For the client authentication, I use keytool to generate a self signed
> certificate by issuing the command:
> keytool -genkey -alias myAlias
> and
> keytool -list -rfc -alias myAlias > client.cer.txt
>
> Removed the header in client.cer.txt, I got a self signed certificate.
> It just contains "-----BEGIN CERTIFICATE ...... -----END
> CERTIFICATE-----".
>
> Then on the administration server, I installed this certificate as a
> trusted certificate authority.
>
> But when the client tried to talk with the server using this
> certificate, it caught the exception "javax.net.ssl.SSLException:
> Received fatal alert: handshake_failure (no cipher suites in common)",
> while on the server the error is "Error receiving connection
> (SEC_ERROR_BAD_SIGNATURE - Certificate has invalid signature) "
>
> Can anybody tell me what went wrong here?
>
> Thank you,
> -Fujian
It sounds to me like you tried to use a single self-signed certificate as
both a trusted CA and as a client certificate. That won't work with
Communicator, if I recall correctly. You need two certs, a trusted CA cert
and a separate client auth cert that was issued by the trusted CA (that is,
whose issuer name is the subject name of thr CA cert). The server needs to
know the CA cert and trust it for client auth. The browser needs to know
both certs.
--
Nelson Bolyard (at home) Speaking only for myself.