×
Namespaces

Variants
Actions
(Difference between revisions)

Java Security Domains

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Adding missing translation link)
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix metadata)
Line 1: Line 1:
{{ArticleMetaData
+
{{ArticleMetaData <!-- v1.2 -->
 
|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]] -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
Line 6: Line 6:
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->  
+
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
|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 -->
 
|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]] -->
|review-by=<!-- After re-review: [[User:username]] -->
+
|translated-from-title= <!-- Title only -->
|review-timestamp=<!-- After re-review: YYYYMMDD -->
+
|translated-from-id= <!-- Id of translated revision -->
|update-by=<!-- After significant update: [[User:username]]-->
+
|review-by= <!-- After re-review: [[User:username]] -->
|update-timestamp=<!-- After significant update: YYYYMMDD -->
+
|review-timestamp= <!-- After re-review: YYYYMMDD -->
|creationdate=20070330
+
|update-by= <!-- After significant update: [[User:username]]-->
|author=[[User:Hartti]]
+
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20070330
 +
|author= [[User:Hartti]]
 
}}[[Category:Java ME]][[Category:Security]][[Category:Signing and Certification]]
 
}}[[Category:Java ME]][[Category:Security]][[Category:Signing and Certification]]
 
{{FeaturedArticle|timestamp=20100215}}
 
{{FeaturedArticle|timestamp=20100215}}
Line 72: Line 74:
  
 
* [https://www.thawte.com/code-signing/index.html Thawte]
 
* [https://www.thawte.com/code-signing/index.html Thawte]
* [https://www.verisign.com/code-signing/index.html Verisign] - installation [[Signed_HelloWorld_example_MIDlet|test MIDlet]] for this certificate
+
* [https://www.verisign.com/code-signing/index.html Verisign] - installation [[Signed HelloWorld example MIDlet|test MIDlet]] for this certificate
  
 
'''Note''' that there are differences between different phone models on which certificates are installed on the phones. Additionally, the same phone model may have a different set of certificates depending on which region it was sold in. Operator variants of the phones can also have additional changes in the certificate availability.
 
'''Note''' that there are differences between different phone models on which certificates are installed on the phones. Additionally, the same phone model may have a different set of certificates depending on which region it was sold in. Operator variants of the phones can also have additional changes in the certificate availability.
  
Also note that the MIDP specification does not allow new certificates to be added on the phones to allow signing to the trusted 3rd party domain. This is, however, possible on S60 2nd Edition devices due to [[KIJ000555 - Signing certificates for MIDlets|incorrect]] implementation ([http://browndrf.blogspot.com/2006/06/build-and-install-singed-midlet.html instructions]). Some operators have also implemented so-called developer certificates for their devices ([[Sprint Java security domains|Sprint]] and [[China Unicom Java security domains|China Unicom]]). Consequently, make sure to [[How to find the Java signing certificates on the phones|check the available code-signing CA-certificates]] (or check [http://www.developer.nokia.com/Community/Discussion/showthread.php?123626-Certificate-Error-Contact-the-application-supplier-in-Nokia-E61&p=374306 this posting]).
+
Also note that the MIDP specification does not allow new certificates to be added on the phones to allow signing to the trusted 3rd party domain. This is, however, possible on S60 2nd Edition devices due to [[Archived:Signing certificates for MIDlets (Known Issue)]] implementation ([http://browndrf.blogspot.com/2006/06/build-and-install-singed-midlet.html instructions]). Some operators have also implemented so-called developer certificates for their devices ([[Sprint Java security domains|Sprint]] and [[China Unicom Java security domains|China Unicom]]). Consequently, make sure to [[How to find the Java signing certificates on the phones|check the available code-signing CA-certificates]] (or check [http://www.developer.nokia.com/Community/Discussion/showthread.php?123626-Certificate-Error-Contact-the-application-supplier-in-Nokia-E61&p=374306 this posting]).
  
 
==Security Domain policies some carriers that deviate from the standard==
 
==Security Domain policies some carriers that deviate from the standard==
Line 99: Line 101:
 
* [[API access rights on phones, S60 2nd FP2 ver2]], on generic 6680, 6630 (6.03.40)
 
* [[API access rights on phones, S60 2nd FP2 ver2]], on generic 6680, 6630 (6.03.40)
 
* [[API access rights on phones, S60 2nd FP3]], on generic N72
 
* [[API access rights on phones, S60 2nd FP3]], on generic N72
* [[API access rights on phones, S60 3rd]], on generic E61i
+
* [[Archived:API access rights on S60 3rd Edition devices]], on generic E61i
* [[API access rights on phones, S60 3rd FP1]], on generic N95
+
* [[Archived:API access rights on S60 3rd FP1 devices]], on generic N95
* [[API access rights on phones, S60 3rd FP2]], on generic 6210 Navigator
+
* [[Archived:API access rights on S60 3rd Edition devices]], on generic 6210 Navigator
 
* [[API access rights on phones, S60 5th]], on generic N97
 
* [[API access rights on phones, S60 5th]], on generic N97
 
* [[API access rights on phones, Series 40 3rd FP1]], on generic 6131
 
* [[API access rights on phones, Series 40 3rd FP1]], on generic 6131
Line 110: Line 112:
  
 
It is not possible to change the default settings available on the phone, but after MIDlet installation it is possible to change the API access settings from the default to the the available ones (not all options are available to untrusted MIDlets).
 
It is not possible to change the default settings available on the phone, but after MIDlet installation it is possible to change the API access settings from the default to the the available ones (not all options are available to untrusted MIDlets).
* [[How_to_change_the_Java_API_access_settings_on_S60_phones | S60 instructions]]
+
* [[How to change the Java API access settings on S60 phones | S60 instructions]]
* [[How_to_change_the_Java_API_access_settings_on_Series_40_phones | Series 40 instructions]]
+
* [[How to change the Java API access settings on Series 40 phones | Series 40 instructions]]
  
 
==References==
 
==References==

Revision as of 07:05, 28 September 2012

Article Metadata
Article
Created: hartti (30 Mar 2007)
Last edited: hamishwillee (28 Sep 2012)
Featured Article
15 Feb
2010

Contents

Introduction

There are some restrictions for accessing certain method calls and APIs from MIDlets. In those cases it is possible that the user will either be prompted for confirmation to allow a certain method call or the access is blocked altogether, resulting a SecurityException to be thrown.

Making these prompts appear less frequently requires the developer to sign the MIDlet and the user to manually change the API access settings. Signing to the operator or manufacturer domain will remove the prompts completely, but this requires close collaboration with those parties.

Security domains

Mobile information device profile (MIDP) 2.0 specification defines four security domains to which the MIDlet can be installed:

  • Third party protection domain (untrusted 3rd party)
  • Identified third party protection domain (trusted 3rd party)
  • Operator protection domain
  • Manufacturer protection domain

API protection groups

Each of the protection domains have certain level of access to the protected (sensitive APIs). The access rights are grouped to a function groups:

  • Net access (MIDP specification also defines low-level net access, but this has been combined on many phones to the Net access function group)
  • Messaging (MIDP specification also defines restricted messaging)
  • Application auto-start
  • Local connectivity
  • Multimedia recording
  • Read user data (including files and PIM)
  • Write/Edit user data (including files and PIM)
  • Location
  • Landmark store
  • Smart card communication
  • Authentication
  • (Call control)
  • (Phone call)

The MIDlet will have access settings defined to each of the function groups above that are supported by the phone. The setting can be one of the following, defined by the security domain policy of the phone:

  • Always allow / Blanket access
  • Ask first time / Ask once per session
  • Ask every time
  • Not allowed

API access definitions in Java ME standards

Java specifications include a number of versions for the available API access rights (Note that it is possible that there might not be a device available which would support the API access rights exactly the way they are defined in the specification!)

NOTE: The MIDP specification defines that even a trusted 3rd party MIDlet cannot have networking and auto-start permissions simultaneously as Always Allowed!

A MIDlet which has not been signed will be placed in the untrusted domain, which has most restrictions for accessing certain APIs. If the MIDlet has been signed and the corresponding certificate is stored in the certificate store of the phone, the MIDlet will be placed in the protection domain to which the certificate has been tied to (there are some complex checks which are done at the installation time, please see the MIDP 2 specification for more info).

Certificates to sign to a trusted 3rd party domain

If your application passes Java Verified testing, it will be signed with UTI root certificate, which will place your MIDlet to the trusted 3rd party domain. Other common certificates that place your MIDlet to the trusted 3rd party domain are available from:

Note that there are differences between different phone models on which certificates are installed on the phones. Additionally, the same phone model may have a different set of certificates depending on which region it was sold in. Operator variants of the phones can also have additional changes in the certificate availability.

Also note that the MIDP specification does not allow new certificates to be added on the phones to allow signing to the trusted 3rd party domain. This is, however, possible on S60 2nd Edition devices due to Archived:Signing certificates for MIDlets (Known Issue) implementation (instructions). Some operators have also implemented so-called developer certificates for their devices (Sprint and China Unicom). Consequently, make sure to check the available code-signing CA-certificates (or check this posting).

Security Domain policies some carriers that deviate from the standard

As the MIDP spec security domain policy is just a recommendation, some operators have defined their own security domains and API access rights. These include:

Security domain information from other manufacturers than Nokia

Note: Motorola handsets do not support Thawte or VeriSign Certificates, only Motorola certs and JavaVerified [1]

API access settings on real phones

Generic phones also have different versions of the API access rights implemented:

It is not possible to change the default settings available on the phone, but after MIDlet installation it is possible to change the API access settings from the default to the the available ones (not all options are available to untrusted MIDlets).

References

931 page views in the last 30 days.
×