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 how to configure a Certificate Type and trigger an enrollment in a single operation.
Code Example
Copy Code | |
---|---|
<characteristic type="CertificateEnroller"> <characteristic type="Configuration"> <characteristic type="{WWImporters_802.1X_cert}"> <parm name="Template" value="ClientAuth"/> <parm name="ServerName" value="{WWImporters-1}"/> <parm name="NoSSL" value="1" datatype="boolean"/> </characteristic> </characteristic> <characteristic type="Operation"> <characteristic type="Enroll"> <characteristic type="{GUID}"> <parm name=“CertificateTypeFriendlyName” value="{WWImporters_802.1X_cert}"/> </characteristic> </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.