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 over the next few weeks. Thanks for all your past and future contributions.

Archived:Establishing trust between OMA DM server and a Symbian device

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
Code ExampleTested with
Devices(s): Eseries devices
Platform(s): S60 3rd Edition FP1, S60 3rd Edition, FP2
S60 3rd Edition FP1
Created: User:Technical writer 1 (12 May 2009)
Last edited: hamishwillee (29 Jun 2012)



Establishing trust between a device and the DM server is described in OMA Device Management DDF for Policy Management available at Nokia Developer. This article explains the possible ways of establishing trust and the different policies that can be used.


There are two ways to create corporate trust.

Separate mapping for certificate and roles

First, the certificate mapping policy is sent.


The above policy creates a mapping between the certificate and the alias_id. The policy does not create the trust but simply describes that COMCOM is the "short name"/alias for the given certificate.

After this, the roles mapping policy is sent.


The above policy maps the COMCOM role to be the trustedadmin which is the role_id of the COMCOM. This policy will display the device security indicator § in the status pane.

Alternative approach

In this approach, both the certificate and role mappings are done at the same time with a single policy:

File:Certificate roles mapping.txt

The command: {{{1}}} will cause the certificate to be searched directly from the HTTPS session. In Approach 1, the certificate is taken from the policy file itself.

The second approach is an easy way to establish trust as both certificate mapping and roles mapping are handled automatically.

See also

OMA Device Management DDF for Policy Management

This page was last modified on 29 June 2012, at 05:23.
21 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.