|
Question : Expired Self-Issued Certificate
|
|
I have Exchange 2003 SP2 running OWA with a self-issued certificate from the CA running on the local Exchange Server. It was valid for 2004-2006 and expired a few months ago. This normally doesn't matter, we just use it for internal SSL for OWA.
I'm now setting up Microsoft Direct Push, and I got it to work unsecured http. I want to secure the data between the mobile devices and the server by using SSL, but the mobile devices don't like our expired certificate. I recently revoked the certificate to create a new one.
I created a dummy site in IIS, and went through the wizard to create a new certificate, but it hasn't shown up anywhere yet.
Please advise on the best technique for me to run our OWA and Exchange Active Sync under a non-expired Cert so I can continue my project.
Just for sport, I was given a Thanksgiving deadline yesterday on implementing Direct Push for Mobile devices for the company so the boss can see how well it works.
|
Answer : Expired Self-Issued Certificate
|
|
Buy a real cert from a trusted authority. I could be wrong, but I've heard you need a trusted cert for direct push (and rpc over https) to work properly. You can get one for $20/yr at godaddy.com.
|
|
|
|