amset

.info
.co.uk - exchange consultancy
.net - internet based solutions

Broadband - Exchange
Login Scripts - Net Admin
Outlook - Windows Mobile
Windows

Contact - Advertise

AddThis Social Bookmark Button

Windows Mobile

Amazon Store


Console Access using
Terminal Services Client
And Windows 2003 Server

Listen to Music over
Your Network

Network Tools

Registry Editing

Remote Control Your
Music over the Network

SSL Certificates on
Windows Mobile

Synchronise over the Network

Using Bluetooth with
Windows Mobile

The Windows Mobile Emulator

Windows Mobile
Compatibility Information

Windows Mobile
Version
Compatibility
2002 Yes
2003 Yes
5.0 Yes
Article Written Using 2003
SSL Certificates on Windows Mobile

The Windows Mobile operating system has support for the most common root certificates. However if you are using one the less common certificates (for example RapidSSL/FreeSSL) or you are creating your own, then the handheld will constantly prompt about the certificate being invalid. You will also be stopped from using any of the synchronisation features that run over https. To get round these errors, you need to install the certificate on to the device.

Certificate Errors

If you try to install the certificate using other methods, then you might get various error messages including:

  • Cannot access certificate
  • This is not a valid certificate, Please select a valid file

If you are getting these kinds of errors then you need to use another technique to get the certificate installed.

Using the Right Certificate

The choice of the certificate that you are importing to the handheld is important.

If you are generating your own certificates, then that is what you need to import.

If you are putting in a third party certificate that is currently not supported by the handheld, then you need to use the third party's root certificate.

Signed Applications

Either of these processes may not work if your device will only run signed applications. If that is the case then you should look for a mechanism that will remove that requirement, or see if the supplier has provided a signed version of the tool.

Importing the Certificates

There are two methods of importing the certificates

  1. Exporting the certificate to file in to a correct format, copying this across to your device and then importing it. Instructions.
  2. Having the certificate as part of a cabinet file. This is useful if you want to deploy the certificate as part of a wider configuration file or want the file to be downloadable from a web site, using the Windows Mobile device. Instructions.

Questions

Q: Why should I use the root certificate instead of the individual certificate that I am using with my web site?
A: Your own certificate will only be valid for a set period. When that certificate expires you will have to go through the process of replacing the certificate. A root certificate is valid for much longer - probably longer than the device will be valid.
Furthermore, if you are using multiple certificates or your users could access multiple web sites that support that certificate, then the root is already there ready to be supported.

Q: Can I use a wildcard certificate?
A: Wildcard certificates are not supported by the current versions of Windows Mobile 5.0 or the previous versions of Windows Mobile. More information: http://blogs.msdn.com/windowsmobile/archive/2005/11/03/488924.aspx

Q: Are there any cheap certificates that are supported by Windows Mobile without having to go through this hassle?
A: Yes. You can get SSL certificates from Go Daddy or one of their resellers such as Certificates for Exchange. These are trusted by Windows Mobile natively. If you are having problems with getting the root certificates to install with Go Daddy certificates then we have a guide here.

 

Sponsored Links

Last Page Update:
28/06/2007

Back to the Top
Contact Us - Advertise on amset.info
Windows Mobile Index - Home Page


Broadband - Exchange - Login Scripts - Network Admin - Outlook - Windows Mobile - Windows


© Amset IT Solutions Ltd. 1998 - 2008. All rights reserved. Reproduction of any content on this web site is prohibited without express written consent. Use of this web site is subject to our terms and conditions. All trademarks and registered trademarks are property of their respective owners. This site is not endorsed or recommended by any company or organisation mentioned on this site. This site is to provide guidance only and as such we cannot be held responsible for any consequences of following the advice given.