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. Thanks for all your past and future contributions.

Archived:The root certificate for Java Verified is missing in the early Series 40 and S60 2nd Edition devices (Known Issue)

From Wiki
Jump to: navigation, search

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata
Tested with
Devices(s): Nokia 6230, Nokia 3220
Nokia 6600
Created: User:Technical writer 1 (February 3, 2005, updated January 9, 2008)
Last edited: hamishwillee (23 Oct 2013)


Some devices don't have the root certificate for Java Verified (Geotrust CA for UTI), which is needed for the installation of Java Verified tested applications. The shipment of those devices started before the certificate was available.


The Java Verified testing and certification program uses a UTI root certificate (also known as "GeoTrust CA for UTI"). This root certificate is missing from the Nokia 6600, Nokia 6230, and Nokia 3220 devices. When this root certificate is missing, the Java Verified tested applications cannot be installed.


Java Verified applications can be installed if the following attributes are removed from the JAD file: MIDlet-Certificate-1-1 and MIDlet-Jar-RSA-SHA1. Without these lines the MIDlet is treated as untrusted and it thereby gives a warning message during the installation. This makes the application appear as if it were unsigned, but it is possible to install the application similarly as any unsigned application. When the MIDlet-Certificate-1-1 and MIDlet-Jar-RSA-SHA1 are removed, the MIDlet-Permissions attribute becomes redundant and it can be removed as well.

In some cases, updating the firmware may solve the problem.

This page was last modified on 23 October 2013, at 05:45.
37 page views in the last 30 days.