DMAcc Configuration Service Provider
This configuration service provider handles the OMA DM DMAcc management object that stores the OMA DM server-specific settings. These settings are collectively referred to as an OMA DM account. The DMAcc node is the parent to all OMA DM accounts nodes.
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.
The following table shows the default settings for DMAcc. The default security role maps to each subnode unless specific permission is granted to the subnode.
Format | Node |
Roles allowed to query and update setting | Operator
Manager Operator TPS |
DMAcc
The root node for DMAcc object. The following table shows the default settings.Format Node Access Type Get Occurs One Scope Permanent DMAcc/x
A placeholder for one or more SyncML DM account nodes. The "x" is a unique identifier for the OMA DM account settings, making each DMAcc/x node the unique parent node for an account. This node name is assigned by the server at bootstrap. If the device is bootstrapped with the w7 Application Configuration Service Provider, then the value for x is a hash of the server-ID.The following table shows the default settings.
Format Node Access Type Add, Get, Delete, Replace Occurs Zero or more Scope Dynamic DMAcc/x/Addr
Stores various addresses. The type of address stored is specified by the value of the AddrType node.The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs One Scope Dynamic DMAcc/x/AddrType
Specifies the format and interpretation of the x/Addr node value. The value is encoded as inline string, as specified in the following table:Address Type Value Description HTTP 1 URL (See RFC2396) The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs One Scope Dynamic DMAcc/x/PortNbr
Specifies the port number to use for the current bearer, if applicable. This must be a decimal number and must fit within the range of a 16-bit unsigned integer.The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs Zero or one Scope Dynamic DMAcc/x/ConRef
Points to connectivity information that is stored elsewhere in the device. This is used to locate connectivity information that is stored separately from the SyncML DM management object.This should provide a logical link to an existing connectivity object anywhere in the device.
The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs One Scope Dynamic DMAcc/x/ServerId
The server identifier for the current OMA DM account. This value is set during bootstrap.Note After the ServerId is set, it cannot be changed in a regular OMA DM session.
Note In a server trigger, the client treats ServerID as UTF-8 encoding, instead of US-ASCII character. UTF-8 is the super set of US-ASCII.
The following table shows the default settings.
Format chr Access Type Add, Get, Delete Occurs One Scope Dynamic DMAcc/x/ServerPW
Holds the password or secret that the server uses to authenticate itself to the client.The following table shows the default settings.
Format chr Access Type Add, Delete, Replace Occurs One Scope Dynamic DMAcc/x/ServerNonce
Stores the next nonce that the server will use to authenticate itself to the client. Nonce refers to a 'number used once'. It is often a random or pseudo-random number issued in an authentication protocol to ensure that old communications cannot be reused in 'repeat attacks'.The following table shows the default settings.
Format bin Access Type Add, Delete, Replace Occurs One Scope Dynamic DMAcc/x/UserName
Stores the name of the user or device. This information is used in OMA DM authentication.The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs One Scope Dynamic DMAcc/x/ClientPW
Holds the password or secret that the client uses to authenticate itself to the server.The following table shows the default settings.
Format chr Access Type Add, Delete, Replace Occurs One Scope Dynamic DMAcc/x/ClientNonce
Stores the next nonce that the client will use to authenticate itself to the server. Nonce refers to a 'number used once'. It is often a random or pseudo-random number issued in an authentication protocol to ensure that old communications cannot be reused in 'repeat attacks'.The following table shows the default settings.
Format bin Access Type Add, Delete, Replace Occurs One Scope Dynamic DMAcc/x/AuthPref
(Optional) A string-valued parameter who's possible values are the names of the various SyncML authentication types. For example, syncml:auth-md5. If this node is present, the client uses this authentication type when connecting to the server. The use of this node reduces the number of round trips between client and server that would be caused by authentication challenges.The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs Zero or one Scope Dynamic DMAcc/x/Name
(Optional) Stores the name for the current SyncML DM account.The following table shows the default settings.
Format chr Access Type Add, Get, Delete, Replace Occurs Zero or one Scope Dynamic DMAcc/x/Ext
Stores extended parametersThe following table shows the default settings.
Format Node Access Type Get Occurs Once Scope Dynamic DMAcc/x/Ext/Microsoft
Stores Microsoft-specific parametersThe following table shows the default settings.
Format Node Access Type Get Occurs Once Scope Dynamic DMAcc/x/Ext/Microsoft/Role
Specifies the role mask that the DM session runs with when it communicates with the server.If this parameter is not present, the DM session is given the role mask of the DM session that the server is created.
The following table shows the default settings.
Format chr Access Type Get, Replace Occurs Once Scope Dynamic
See Also
Configuration Service Provider Reference for Windows Mobile-Based Devices | DMAcc DDF File | DMAcc Configuration Service Provider Examples for OMA DM
Send Feedback on this topic to the authors