Hi.
We have an internal CA that is used for all of your certificates.
These certificates work with both Windows and Linux.
However, although we can successfully import the CA certificate into the phone. It will not actually have an SSL conversation. The SSL certificates generated work fine with Windows, Linux, and every SSL application so far. So we do not believe its the certificates, but maybe the way the CA generates the certificates that the phone does not like.
Any help would be appreciated.
Self signed certificates are working on my N95. The trick is using the right ones. When you have a CA server and request a certificate, the server actually ends up with two, a client certificate, which is sent whenever you access information that you want encrypted with that certificate, and a root certificate. The root certificate is automatically generated when you set up a CA server and is stored on the server, somewhere. You need to install that root certificate to the N95. I used CA-Cert certificates, because downloaded the root certificate when I need it is very easy from their website. I have Dataviz Roadsync running on the N95, and use ssl to encrypt sync data to an Exchange Server. It works very well.
Hope this helps.
Mike
I have installed the CA root certificate on my N95.
It installs successfully but the communication fails with the server.
However I can read the details of the root CA certificate without issue.
Is there any possibility that the issue is that the CA generated a certificate that Symbian believes is errorneous?
Since the Symbian doesn't even complain about the certificate being untrusted or invalid. It simply does not work and errors back into the application.
Another update. It seems to work fine with this application when using a self-signed cert. Even when expired. So it would seem that the CA signed cert is doing something the phone is not expecting, and thus throwing an error.
The self signed cert we tested was expired. The CA signed one is currently valid.