w7 APPLICATION Configuration Service Provider Example for OMA Client Provisioning

4/8/2010

This example shows how to use the w7 APPLICATION configuration service provider to create an OMA DM account during the bootstrap process. W7 is the APPID.

Code Example

<wap-provisioningdoc version="1.1">
  <characteristic type="APPLICATION">
    <parm name="APPID" value="w7"/>
    <parm name="PROVIDER-ID" value="com.thephone-company.manage"/>
    <parm name="NAME" value="Mgmt Server"/>
    <parm name="SSLCLIENTCERTSEARCHCRITERIA" value="Subject=CN%3DTest%2CO%3DContoso&Stores=MY%5CSystem%EF%80%80MY%5CUser"/>
    <parm name="ADDR" value="https://www.thephone-company.com/manage"/>
    <parm name="ROLE" value="24"/>
    <characteristic type="APPAUTH">
      <parm name="AAUTHLEVEL" value="APPSRV"/>
      <parm name="AAUTHTYPE" value="DIGEST"/>
      <parm name="AAUTHNAME" value="clientname"/>
      <parm name="AAUTHSECRET" value="clientsecret"/>
      <parm name="AAUTHDATA" value="clientnonce"/>
    </characteristic>
    <characteristic type="APPAUTH">
      <parm name="AAUTHLEVEL" value="CLIENT"/>
      <parm name="AAUTHTYPE" value="DIGEST"/>
      <parm name="AAUTHSECRET" value="serversecret"/>
      <parm name="AAUTHDATA" value="servernonce"/>
    </characteristic>
  </characteristic>
  <! — other characteristic -- >
</wap-provisioningdoc>

Remarks

For the device to decode correctly, provisioning XML that contains the APPLICATION characteristic must support OMA Client Provisioning version 1.1.

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

Reference

APPLICATION Configuration Service Provider

Concepts

Configuration Service Provider Reference for Windows Mobile Devices