Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

This example shows the output from the parm query.

Code Example

Copy Code 
<characteristic type="CertificateStore">
   <characteristic type="Privileged Execution Trust
Authorities">
	<characteristic type="{hash of certificate}">
		 <parm name="EncodedCertificate" value="{encoded hash of
certificate}"/>
		 <parm name="Role" value="0"/>
	</characteristic>
   </characteristic>
   <characteristic type="Unprivileged Execution Trust
Authorities">
	<characteristic type="{hash of certificate}">
		 <parm name="EncodedCertificate" value="{hash of
certificate}"/>
	</characteristic>
   </characteristic>
   <characteristic type="SPC">
	<characteristic type="{hash of certificate}">
		 <parm name="Role" value="63"/>
		 <parm name="IssuedBy" value="Test Root Authority"/>
		 <parm name="ValidTo" value="1/1/2020 9:43:02AM"/>
	</characteristic>
   </characteristic>
</characteristic>

Remarks

One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must replace the values as appropriate, and add the node as a child of the OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

See Also