China Unicom Java security domains
m |
hamishwillee
(Talk | contribs) m (Hamishwillee - Bot update - Add ArticleMetadata) |
||
| (4 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Category:Java]][[Category:Signing and Certification]] | + | {{ArticleMetaData <!-- v1.2 --> |
| − | In general China Unicom has | + | |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]]) --> | ||
| + | |devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') --> | ||
| + | |sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) --> | ||
| + | |platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later --> | ||
| + | |devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) --> | ||
| + | |dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 --> | ||
| + | |signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer --> | ||
| + | |capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. --> | ||
| + | |keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase --> | ||
| + | |language= <!-- Language category code for non-English topics - e.g. Lang-Chinese --> | ||
| + | |translated-by= <!-- [[User:XXXX]] --> | ||
| + | |translated-from-title= <!-- Title only --> | ||
| + | |translated-from-id= <!-- Id of translated revision --> | ||
| + | |review-by= <!-- After re-review: [[User:username]] --> | ||
| + | |review-timestamp= <!-- After re-review: YYYYMMDD --> | ||
| + | |update-by= <!-- After significant update: [[User:username]]--> | ||
| + | |update-timestamp= <!-- After significant update: YYYYMMDD --> | ||
| + | |creationdate= 20070720 | ||
| + | |author= [[User:Hartti]] | ||
| + | }} | ||
| + | [[Category:Java ME]][[Category:Signing and Certification]] | ||
| + | In general, China Unicom has disabled many capabilities for untrusted 3rd-party applications, including | ||
* platformRequest() | * platformRequest() | ||
* Network connections | * Network connections | ||
| Line 10: | Line 32: | ||
* UniJa Standby Mode | * UniJa Standby Mode | ||
| − | There is no trusted 3rd party domain. | + | There is no trusted 3rd-party domain. |
One has to sign the MIDlet with a certificate from China Unicom. This operator domain has full access to all APIs. | One has to sign the MIDlet with a certificate from China Unicom. This operator domain has full access to all APIs. | ||
| − | There is also a China Unicom testing certificate available, which is valid for 21 days. It is required to apply again when the | + | There is also a China Unicom testing certificate available, which is valid for 21 days. It is required to apply again when the validity period is exceeded. |
Latest revision as of 09:32, 18 July 2012
Article Metadata
In general, China Unicom has disabled many capabilities for untrusted 3rd-party applications, including
- platformRequest()
- Network connections
- Messaging
- PushRegistry
- Local connectivity
- PIM access (read and edit)
- UniJa 3D Graphics
- UniJa Standby Mode
There is no trusted 3rd-party domain.
One has to sign the MIDlet with a certificate from China Unicom. This operator domain has full access to all APIs.
There is also a China Unicom testing certificate available, which is valid for 21 days. It is required to apply again when the validity period is exceeded.
