×
Namespaces

Variants
Actions
(Difference between revisions)

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

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot change of template (Template:KnowledgeBase) - now using Template:ArticleMetaData)
debjit.roy (Talk | contribs)
(Debjit.roy -)
Line 1: Line 1:
 +
[[Category:Symbian C++]][[Category:S60 3rd Edition FP1]][[Category:Technical Solution]][[Category:Device Management]]
 
__NOTOC__
 
__NOTOC__
 
__NOEDITSECTION__
 
__NOEDITSECTION__
Line 19: Line 20:
 
|author=[[User:Technical writer 1]]
 
|author=[[User:Technical writer 1]]
 
}}
 
}}
 
+
{{Archived|timestamp=20120223112842|user=roy.debjit| }}
 
== Description ==
 
== Description ==
  
Line 55: Line 56:
 
==See also==
 
==See also==
 
[http://www.developer.nokia.com/info/sw.nokia.com/id/2ff7409a-cbb3-4151-bbae-247aac7cda33/OMA_Device_Management_DDF_for_Policy_Management_v1_1_en.zip.html OMA Device Management DDF for Policy Management]
 
[http://www.developer.nokia.com/info/sw.nokia.com/id/2ff7409a-cbb3-4151-bbae-247aac7cda33/OMA_Device_Management_DDF_for_Policy_Management_v1_1_en.zip.html OMA Device Management DDF for Policy Management]
 
[[Category:Symbian C++]][[Category:S60 3rd Edition FP1]][[Category:Technical Solution]][[Category:Device Management]]
 

Revision as of 14:28, 23 February 2012

Template:KBTS

Article Metadata
Tested with
Devices(s): Eseries devices
Compatibility
Platform(s): S60 3rd Edition FP1, S60 3rd Edition, FP2
S60 3rd Edition FP1
Article
Created: User:Technical writer 1 (12 May 2009)
Last edited: debjit.roy (23 Feb 2012)

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}}.

Description

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.

Solution

There are two ways to create corporate trust.

Separate mapping for certificate and roles

First, the certificate mapping policy is sent.

File:Certificate mapping.zip

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.

File:Roles mapping.zip

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: use_bearer_certificate = "true" 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

90 page views in the last 30 days.
×