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.

Revision as of 06:13, 3 July 2012 by hamishwillee (Talk | contribs)

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

Requesting extended capabilities set for Developer Certificates

From Wiki
Jump to: navigation, search

Needs-update.pngThis article needs to be updated: If you found this article useful, please fix the problems below then delete the {{ArticleNeedsUpdate}} template from the article to remove this warning.

Reasons: hamishwillee (23 Nov 2011)
The process if now completely different - devcerts are requested by specifying IMEIs etc through the site and access to more powerful capabilities is granted by verifying your account. This article is therefore completely incorrect and needs to be updated or deleted.

Article Metadata
Code ExampleCompatibility
Platform(s): S60 3rd Edition,
S60 3rd Edition, FP1
S60 3rd Edition FP1
S60 3rd Edition (initial release)
Created: User:Technical writer 2 (05 Oct 2006)
Last edited: hamishwillee (03 Jul 2012)


Requesting extended capabilities set for Developer Certificates


The process works as follows:

  1. Register for free as a user at
  2. Download a tool called Developer Certificate Request Tool from File:DevCertRequest
  3. Within Developer Certificate Request Tool (DCRT for short), you generate a Certificate Request File, specifying also the following information:
    1. ACS Publisher ID or self-created private key.
    2. Data such as Company Name, city, etc.
    3. The IMEI(s) of the phone you will use to test your application (you can find out this information by typing *#06# on the phone's keyboard).
    4. The set of capabilities needed.
  4. After you generate a .csr file, go to, upload your .csr file, and the system will generate a Developer Certificate for you.
  5. This Developer Certificate has all the capabilities you specified in step 3.4, so you must use it to sign your application, and then install it on the phone.

All these 5 steps can be gone through without an ACS Publisher ID. However, restrictions apply:

  1. You can test the application with a single phone. No multiple IMEIs are allowed.
  2. You have a restricted set of capabilities: LocalServices, Location, NetworkServices, PowerMgmt, ProtServ, Read User Data, SurroundingsDD, SW Event, User Environment, Write User Data.

If you buy an ACS Publisher ID, you'll get:

  1. Extended capabilities set: Read/Write Device Data, TrustedUI.
  2. Your Developer Certificate will allow you to specify up to 20 IMEIs in the DevCertRequest tool, so you can test your application with more phones.

In order to use those advanced settings, go to the Developer Certificate Request Tool, and in step 3.1 above, specify the paths for your ACS Publisher ID, instead of a self-created private key. The tool will then allow you to specify more capabilities (including Read/Write Device Data) for the Certificate Request File it generates.

Then upload your .csr file to the same URL above, and you'll get an unrestricted Developer Certificate you can use to test your application with up to 20 phones, with the IMEIs you specified in step 3.3.

Please also note that, unless you purchase an ACS Publisher ID, you won't be able to submit your application to Symbian Signed program to test & certify it after it's finished. With that said, it is recommended you purchase the ACS early on the development process, so you can take advantage of its features right away.

This page was last modified on 3 July 2012, at 06:13.
36 page views in the last 30 days.