SecurityPolicy Configuration Service Provider
Use the SecurityPolicy Configuration Service Provider to configure security policy settings.
Note This Configuration Service Provider can be managed over both the OMA Client Provisioning (formerly WAP) and the OMA DM protocol.
Note Access to this Configuration Service Provider is determined by Security roles. Because OEMs and Mobile Operators can selectively disallow access, ask them about the availability of this Configuration Service Provider. For more information about roles, see Security Roles and Default Roles for Configuration Service Providers.
The following image shows the management object used by OMA DM.
.gif)
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
.gif)
Characteristics
Only the root characteristic is available. The following table shows the default settings for all parameters in this Configuration Service Provider. The default security role maps to each subnode unless specific permission is granted to the subnode.
| Permissions | Read/write |
| Roles allowed to query and update setting | Manager |
Parameters
<policy ID>
Identifies a security policy. Security Policies are indexed by the decimal representation of the policy ID, which is a DWORD value. The VALUE of the policy is also a DWORD. These policies can only be changed by the manager of the device. For a detailed description of each security policy, including possible values, see Security Policy Settings.The following table shows the default settings.
Permissions Read/Write Data type Integer Roles allowed to query and update setting Manager
Microsoft Custom Elements
The following table shows the Microsoft custom elements that this Configuration Service Provider supports for OMA Client Provisioning.
| Elements | Available |
|---|---|
| parm-query | Yes |
| noparm | Yes. If this is used, then the policy is set to 0 by default (corresponding to the most restrictive of policy values). |
| nocharacteristic | No |
| characteristic-query | No |
Use these elements to build standard OMA Client Provisioning (formerly WAP) configuration XML. For information about specific elements, see MSPROV DTD Elements. For examples of how to generally use the Microsoft custom elements, see Provisioning XML File Examples.
For information about OMA Client Provisioning, see OMA Client Provisioning Files.
See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | SecurityPolicy Configuration Service Provider Examples for OMA Client Provisioning | Default Security Policy Settings for Windows Mobile-Based Devices
Send Feedback on this topic to the authors