A solution for SSL Certificates and ActiveSync problems
Further to my previous posts Mobile ActiveSync and Microsoft Exchange 2007 and SSL Certificates for Exchange Server 2007 continued… I am happy to report that I’m finally making progress on the ongoing SSL certificate/ActiveSync debacle. I dug out my Blackberry 8820 to test the certificate problem and of all things the Blackberry gave the clearest indicator of what the problem was – leading me to the discovery that some mobile devices only seem to read the first entry name entry in certificates that support multiple names.
A little digging and a few penny drops later and I managed to get ActiveSync working properly on the Sony Ericsson p1i. I had put the server address into the p1i as mail.domainname.com (I also tried www.domainname.com) but the certificate we applied for listed domainname.com as the first entry followed by www.domainname.com, mail.domainname.com, autodiscover.domainname.com, host. Of course the p1i seemed to be checking only the first entry and considered that www.domainname.com (the entry I had put in for the server) and domainname.com (the first entry on the certificate) were completely different entities thus throwing up a certificate violation warning.
It seems that although the certificate and Exchange 2007 support (SAN) Subject Alternate Naming – that in actual fact certain mobile devices don’t and as such the order of the addresses in the certificate, particular the first one, is vital. The p1i is now syncing quite happily using ActiveSync and push. Mind you, I still haven’t got the iPAQ working using ActiveSync but I’m getting closer!
Pingback: blackberry 8820 t mobile
Pingback: microsoft activesync