|
|||||||||||||||||
 |
|||||||||||||||||
 |
|
|
|
DevCerts overview
Symbian Signed Developer Certificates (DevCerts)
The enhanced platform-wide security framework introduced in Symbian OS v9 provides greater security for both phone and network by restricting access to certain system APIs using a trust-based 'capability' model.
Therefore if a developer wishes to access capabilities enabling certain restricted APIs, a DevCert may be required to test and debug the application on a target device. After the developer has finished testing and debugging they can submit their application through the Symbian Signed process.
The majority of Symbian OS v9 applications will not require DevCerts. Here are some tips on how to avoid needing to access the restricted APIs>>
DevCerts provide controlled access to certain capabilities on the Symbian OS phone itself. This will also limit the number of target phones (IMEIs) which the DevCert signed application can access. DevCerts are valid for six months and are application specific. The complete DevCert process is hosted and managed on the Symbian Signed website>>
There are four scenarios concerning access to capabilities: no grant required, the user grants them, the DevCert grants access to sensitive capabilities or phone manufacturer approval is required. Sony Ericsson is only involved in the last two scenarios which both follow similar processes:
Below is an overview of which capabilities are involved:
DevCert process overview
Here's a brief overview of process steps for both DevCert scenarios. More information, including a detailed step-by-step guide, is available on the Symbian Signed website>> Sensitive capabilities DevCert process
1. Register on www.symbiansigned.com and the following process is managed on that website.
2. Download the DevCertRequest tool to generate a Certified Symbian Request (.csr) file. This tool guides you through five steps:
a. Name of application
b. File information c. Personal information d. Phone IMEI and capabilities information e. Confirm Symbian Developer Request Details 3. Request a new DevCert by uploading the .csr file which generates a DevCert file ready for download.
4. Use the DevCert file to create a SIS file to enable testing on the specified phone.
Once the DevCert process is completed, the application tested and ready for commercialization, the standard Symbian Signed process continues.
Phone manufacturer approved capabilities DevCert process
Similar process to above but with key differences to access restricted APIs: 1. Register on www.symbiansigned.com and the following process is managed on that website.
2. Download DevCertRequest tool to generate a Certified Symbian Request (.csr) file. This tool guides you through five steps:
a. Name application
b. File information, including ACS Publisher ID c. Personal information d. Phone capabilities request. Check the 'Enable Phone Manufacturer Capabilities' box to pick from the restricted APIs list. If no ACS Publisher ID is entered, there will be no list of manufacturer restricted APIs. e. Confirm Symbian Developer Request Details 3. To request a Phone Manufacturer Approved DevCert for Sony Ericsson smartphones you need to complete the following six-step process:
a. Select 'Sony Ericsson' as phone manufacturer
b. Information about the Phone Manufacturer DevCert c. Developer contact details d. Request details including number of IMEIs, rational for accessing the requested phone manufacturer APIs and provide application details e. Business reasons for requiring access to restricted APIs. f. Upload the .csr file This request will then be forward to Sony Ericsson. A Sony Ericsson steering group will then review all requests to access the phone manufacturer APIs with due diligence and their decision will be communicated to the developer via Symbian Signed. More information on Sony Ericsson's approval criteria>>
Channel Certification Once the Phone Manufacturer Approved DevCert is accepted, the application tested and ready for commercialization, there is an extended Symbian Signed process called Channel Certification. Here's an overview of the process: 1. Complete the Sony Ericsson request form>>
2. Sony Ericsson checks and reviews information submitted against the previously made DevCert request.
3. Sony Ericsson grants the developer access to a login protected Sony Ericsson channel certifier web page on the Symbian Signed website. This enables you to submit your application to be tested against the Symbian Signed test criteria plus the Sony Ericsson
criteria.
4. The extended Symbian Signed process will follow the standard Symbian Signed process, and the test success or failure is managed by the selected test house.
More information:
|
|
|
|
|
|
|
|
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
v9 based phones before submitting them for signing. 
 |
| Published by Sony Ericsson Developer World |
 |