https errors for when client authentication

Hi all,

I encountered the error when i configured the web server to require client authentication. Can anyone advise?

[01/Jun/2006:15:41:08] failure (17048): HTTP3068: Error receiving request from 1

0.60.20.126 (SSL_ERROR_NO_TRUSTED_LIBSSL_CLIENT_CA: the CA that signed the clien

t certificate is not trusted locally)

Regards

Ken

[373 byte] By [keneio] at [2007-11-26 7:41:14]
# 1

Hi Ken,

This means that the type of certificate that you are using is not trusted, and therefore cannot be used. You have two options:

1) Use one of the supported types, e.g. Verisign

or

2) The upcoming release of WebServer 7.0 supports self-signed certificates, so perhaps you should try downloading a preview build and trying it out. You can get it here:

http://www.sun.com/download/products.xml?id=446518d5

Hope this helps

roho at 2007-7-6 19:47:47 > top of Java-index,Web & Directory Servers,Web Servers...
# 2

The message "the CA that signed the client certificate is not trusted locally" means that the CA that signed the *client* certificate (i.e. the cert that 10.60.20.126 sent to the server, here) is not trusted locally (i.e. by the web server).

For SSL client auth the clients must have certs signed by some CA which is trusted by the web server. If the client has a cert issued by a known CA (like Verisign and others), those are trusted by default. I suspect here the client has a cert issued by some local CA. You need to import that CA's cert into the web server and mark it trusted.

jyri at 2007-7-6 19:47:48 > top of Java-index,Web & Directory Servers,Web Servers...
# 3
Am I to assume from this that iPlanet 6.0 doesn't support self-signed certificates? I've just gotten the same error message about "not trusted locally" and I can't see any option to make a certificate locally trusted. Regards,Jim Lane
JimLane at 2007-7-6 19:47:48 > top of Java-index,Web & Directory Servers,Web Servers...
# 4
There isn't anything special about self-signed certificates. The same requirements hold. In that case, the "CA which signed the cert" just happens to be the same one as the entity of the cert itself. So, that cert needs to be trusted as a CA.
jyri at 2007-7-6 19:47:48 > top of Java-index,Web & Directory Servers,Web Servers...
# 5
So what do I have to do to my self-signed certificate to get it to be "trusted as a CA"?
JimLane at 2007-7-6 19:47:48 > top of Java-index,Web & Directory Servers,Web Servers...