Share via


VPN Configuration Service Provider Example for OMA DM

4/8/2010

The following example can be used as a template to configure settings for the VPN configuration service provider. The VPN object in this example defines a VPN connection from GPRS1 and WiFi2. A corresponding ACCESS entry must be created which maps this VPN object to its destination metanetwork (for example, Work). The example specifies corp-vpn.mycompany.com as the VPN access point and uses IPSec certificate authentication.

Code Example

<atomic>
<CmdID>8000</CmdID>
  <add>
    <CmdID>8001</CmdID>
    <Item>
      <Target>
        <LocURI>./Vendor/MSFT/VPN/VPN0/VPNID</LocURI>
      </Target>
      <Meta>
        <Format xmlns='syncml:metinf'>chr</Format>
      </Meta>
      <Data>MS-VPN1</Data>
    </Item>
  </add>
  <add>
    <CmdID>8002</CmdID>
    <Item>
      <Target>
        <LocURI>./Vendor/MSFT/VPN/VPN0/NAME</LocURI>
      </Target>
      <Meta>
        <Format xmlns='syncml:metinf'>chr</Format>
      </Meta>
      <Data>VPN1</Data>
    </Item>
  </add>
  <add>
    <CmdID>8003</CmdID>
    <Item>
      <Target>
        <LocURI>./Vendor/MSFT/VPN/VPN0/ADDR</LocURI>
      </Target>
      <Meta>
        <Format xmlns='syncml:metinf'>chr</Format>
      </Meta>
      <Data>corp-vpn.adatum.com</Data>
    </Item>
  </add>
  <add>
    <CmdID>8004</CmdID>
    <Item>
      <Target>
        <LocURI>./Vendor/MSFT/VPN/VPN0/ADDRTYPE</LocURI>
      </Target>
      <Meta>
        <Format xmlns='syncml:metinf'>chr</Format>
      </Meta>
      <Data>IPV4</Data>
    </Item>
  </add>
  <add>
    <CmdID>8005</CmdID>
    <Item>
      <Target>
        <LocURI>./Vendor/MSFT/VPN/VPN0/CONREFS/CONREF0/ConRef</LocURI>
      </Target>
      <Meta>
        <Format xmlns='syncml:metinf'>chr</Format>
      </Meta>
      <Data>GPRS1</Data>
    </Item>
  </add>
    <CmdID>8006</CmdID>
    <Item>
      <Target>
        <LocURI>./Vendor/MSFT/VPN/VPN0/CONREFS/CONREF1/ConRef</LocURI>
      </Target>
      <Meta>
        <Format xmlns='syncml:metinf'>chr</Format>
      </Meta>
      <Data>WiFi2</Data>
    </Item>
  </add>
    <add>
      <CmdID>8007</CmdID>
      <Item>
        <Target>
          <LocURI>./Vendor/MSFT/VPN/VPN0/AUTHINFO/AUTHTYPE</LocURI>
        </Target>
        <Meta>
          <Format xmlns='syncml:metinf'>chr</Format>
        </Meta>
        <Data>IPSECL2TP</Data>
      </Item>
    </add>
    <add>
      <CmdID>8007</CmdID>
      <Item>
        <Target>
          <LocURI>./Vendor/MSFT/VPN/VPN0/AUTHINFO/AUTHNAME</LocURI>
        </Target>
        <Meta>
          <Format xmlns='syncml:metinf'>chr</Format>
        </Meta>
        <Data>mydomain\myuser</Data>
      </Item>
    </add>
    <add>
      <CmdID>8008</CmdID>
      <Item>
        <Target>
          <LocURI>./Vendor/MSFT/VPN/VPN0/AUTHINFO/AUTHSECRET</LocURI>
        </Target>
        <Meta>
          <Format xmlns='syncml:metinf'>chr</Format>
        </Meta>
        <Data>mysecret</Data>
      </Item>
    </add>
    <add>
      <CmdID>8009</CmdID>
      <Item>
        <Target>
          <LocURI>./Vendor/MSFT/VPN/VPN0/AUTHINFO/IPSECINFO/AUTHTYPE</LocURI>
        </Target>
        <Meta>
          <Format xmlns='syncml:metinf'>chr</Format>
        </Meta>
        <Data>Cert</Data>
      </Item>
    </add>
</atomic>

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 SyncBody node in an OMA DM provisioning file.

You must also configure the ACCESS Configuration Service Provider before using this example and enable the connections "GPRS1" and "WiFi2".

See Also

Reference

VPN Configuration Service Provider