Namespaces

Variants
Actions

Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

Revision as of 02:42, 25 July 2013 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Thawte signing for Java ME

From Wiki
Jump to: navigation, search

This document describes how to code sign a Java ME app using Thawte. This is one of two mechanisms for avoiding security messages when accessing secured APIs.

Article Metadata
Article
Created: awoywood (02 Sep 2009)
Last edited: hamishwillee (25 Jul 2013)

Contents

Introduction

Let's assume you want to get rid of those annoying security messages when accessing JSR-75 (or another), what can you do? There are 2 main ways to reduce the number of messages:

This document describes how to code sign a Java ME app using Thawte (the alternative is to use Verisign). Thawte provides certificates for US$ 299, cheaper than Verisign, and I just followed the whole process, so I'll describe the process, as it worked for me.

1) Generate keystore and CSR for JavaSoft Certificate

Follow this document from Thawte: Solution SO3186

You will use a tool from Sun called keytool.

You will end up with a keystore (which is basically a file where your keys are stored) and a CSR, which is a text that you must send to Thawte.

2) Buy certificate from Thawte

3) Prove Thawte that "you are you".

They'll ask you more information and maybe documents. In my case, our company is located outside the US (in Chile) and the whole process took 2 weeks. I guess if you are in the US, it will be much faster.

4) Import the certificate into your keystore

Read this small document from Thawte Solution SO1079

5) Sign your application

For this step, there is no information in Thawte's site. You may find this document Solution SO7517, but it's about signing standard jars, not midlets.

If you like working with the console, you may follow the instructions from Verisign Sign Midlet Suites with JadTool or read more deeply about Sun's JADtool.


But I recommend you turn to Netbeans (I guess Eclipse will have a similar feature).

Open up your project, go to its Properties and the Signing tab. Check the "Sign Distribution" option and click in "Open Keystores Manager". Here you need to add the keystore you created in the step 1. Be sure to unlock your keystore and then your key.

Next, rebuild your project and Viola! Your application is signed!

To verify it, open the jad file. You will notice a number of new lines regarding the certification stuff. Also, your jar file will be a bit bigger than without the signing.

This page was last modified on 25 July 2013, at 02:42.
74 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.

 

Thank you!

We appreciate your feedback.

×