×
Namespaces

Variants
Actions
(Difference between revisions)

Verisign signing - Java ME

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
hamishwillee (Talk | contribs)
m (Hamishwillee - Fix categories)
 
Line 1: Line 1:
 +
[[Category:Signing and Certification on Java ME]][[Category:How To]]
 
{{ArticleMetaData <!-- v1.1 -->
 
{{ArticleMetaData <!-- v1.1 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
Line 9: Line 10:
 
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 
|id= <!-- Article Id (Knowledge base articles only) -->
 
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 
|translated-by= <!-- [[User:XXXX]] -->
 
|translated-by= <!-- [[User:XXXX]] -->
Line 91: Line 90:
  
 
* [http://download.oracle.com/javame/config/cldc/cldc-opt-impl/sjwc-2.0-web/docs/ToolsGuide-html/jadtool.html#50556936_22809 Sun Signing]
 
* [http://download.oracle.com/javame/config/cldc/cldc-opt-impl/sjwc-2.0-web/docs/ToolsGuide-html/jadtool.html#50556936_22809 Sun Signing]
 
[[Category:Java ME]][[Category:How To]][[Category:Security on Java ME]][[Category:Signing and Certification]][[Category:Java ME]]
 

Latest revision as of 05:47, 25 July 2013

Article Metadata
Article
Created: senthil_k (29 Jan 2008)
Last edited: hamishwillee (25 Jul 2013)


A commercial application which requires access to some specific APIs like JSR 75, JSR 205, JSR 135 etc. benefits from getting signed with a commercial certificate from third party certificate providers like VeriSign or Thawte. Before buying any certificate from these third parties, you have to make sure that the target phone's of your device has the corresponding root certificate installed and set to allow MIDlet signing. You can check this from the settings of the target mobile device.

The following paragraphs contain the description of the process and steps required to get a certificate from VeriSign and to sign & test you MIDlet.

Contents

[edit] Getting the certificate

[edit] Step 1

Make sure, you have the latest JDK installed on your computer.

[edit] Step 2

Create a keystore

You have to generate a public/private key pair, for this enter the following command, specifying a name for your keystore and an alias as well.

C:\jdk1.3\bin\keytool -genkey -keyalg rsa -keystore <keystore_filename> -alias <alias_name>

Keytool prompts you to enter a password for your keystore, your name, organization, and address. The public/private key pair generated by keytool is saved to your keystore and will be used to sign J2ME applications. This key is never sent to VeriSign and is required to sign code. So you should make a copy of the public/private key pair and store it in a safe deposit box or other secure location. If the key is lost or stolen, contact VeriSign immediately to have it revoked.

[edit] Step 3

Create a CSR

You need to generate a Certificate Signing Request (CSR) for the enrollment process.

1. The following command requests Keytool to create a CSR for the key pair in the keystore:

 C:\jdk1.3\bin\keytool -certreq -file certreq.csr -keystore <keystore_filename> -alias <alias_name>

2. Begin the enrollment process for a Code Signing ID from the products and services section of the VeriSign Web site.

3. Copy the contents of the CSR and paste them directly into the VeriSign enrollment form. Open the file in a text editor that does not add extra characters (Notepad or Vi are recommended).

This is the end of requesting the certificates from VeriSign.

[edit] Signing the MIDlet

[edit] Step 1

After VeriSign has verified your request, they will send an email with the digital id attached. You have to import it to the keystore.

To import your Sun Java Signing Code Signing Digital ID into your keystore, enter the following code with the path correct name for your file (for example, "cert.cer") to your Code Signing Digital ID.

C:\jdk1.3\bin\keytool -import -trustcacerts -keystore <keystore_filename> -alias <alias_name> -file cert.cer

[edit] Step 2

Now sign the application by the two command prompt

java -jar JadTool.jar [ -addcert -alias keyAlias [ -keystore keystore ] [ -storepass password ]   -inputjad inputJadFile -outputjad outputJadFile ]
java -jar JadTool.jar [ -addjarsig [ -jarfile jarFile ] -alias keyAlias [ -keystore keystore ]  -storepass password -keypass keyPassword    -inputjad inputJadFile -outputjad outputJadFile ]

For all the signing steps, Courtesy:

This page was last modified on 25 July 2013, at 05:47.
221 page views in the last 30 days.