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

The ACCESSconfiguration service provider (CSP) specifies destination networks to which multiple connectivity objects and proxy or Virtual Private Network (VPN) connections can connect. It also specifies the URL domain mappings for each of these destination networks.

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 Rolesand Default Roles for Configuration Service Providers.

ACCESS specifies one or more domains. The collection of these domains constitutes a destination network, which you can connect to through either multiple connectivity objects (for example, the Internet) or through a specific connectivity object, for example Multimedia Messaging Service (MMS). ACCESS also supports scenarios in which multiple work networks can be accessed by different sets of network connectivity objects.

Because ACCESS enables you to specify multiple domains under each entry, you can use it to add as many URL exceptions as are required for each defined network, in addition to the standard URL mappings.

In addition to supporting destination networks based on URL domain mapping, ACCESS also supports destination networks based on specific applications. If an application uses a magic URL(a URL beginning with a protocol other than HTTP) the application can be mapped to a network using only the ACCESS configuration service provider. Otherwise, an application must use the ConnMgrMapConRefAPI or a registry key (in addition to the ACCESS configuration service provider) to map to a specific network.

Note:
This configuration service provider is part of the OMA DM protocol, with some proprietary extensions, and must be used when provisioning devices using OMA DM. To provision devices using the OMA Client Provisioning protocol, use the CM_Mappings Configuration Service Providerand the CM_Networks Configuration Service Providerinstead.

ACCESS mappings to metanetworks cannot be deleted using the Windows Mobile user interface, but network access points provisioned using the NAP configuration service provider can. When reprovisioning a network access point after it has been deleted, you must delete and reprovision the corresponding ACCESS mappings before reconfiguring the network using NAP.

The following image shows the management object used by OMA DM.

ACCESS

The root node for the ACCESS object. The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

Access Type

Read/Write

Occurs

Once

ACCESS/Internet

Specifies the domain names, application-specific connection preferences, and port number-specific connection preferences for the Internet metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/Work

Specifies the domain names, application-specific connection preferences, and port number-specific connection preferences for the Work metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/WAP

Specifies the domain names, application-specific connection preferences, and port number-specific connection preferences for the WAP metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/SecureWAP

Specifies the domain names, application-specific connection preferences, and port number-specific connection preferences for the SecureWAP metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/ XXX /Domains

Specifies the domain names associated with the parent metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/ XXX /Domains/DomainName XXX /DomainName

A regular expression that specifies a set of URLs associated with the great-grandparent metanetwork. DomainNameXXX holds a string containing a decimal value that represents the mapping index. For more information on mapping index values, see CM_Mappings Configuration Service Provider.

The following table shows the default settings.

Data Type

String

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/ XXX /ConRefs

Specifies all connectivity objects, proxy connections, and VPN connections associated with the parent metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/ XXX /ConRefs/ConRef XXX /ConRef

Specifies a single connectivity object, proxy connection, or VPN connection associated with the great-grandparent metanetwork. The value must be the entry name of a connection, which may be the initial node on a path connecting the device to the specified destination network.

The suggested name of this node is ConRef XXX, a numbered node beginning at zero. For example, if you have two connectivity objects associated with a metanetwork, you would use two nodes, ConRef0 and ConRef1. You would specify the name of the object in the ConRef child of the numbered node. You can use any unique name for this node, but no spaces may appear in the node name (use %20instead).

The following table shows the default settings.

Data Type

String

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/XXX/Ext

Stores extended parameters.

ACCESS/XXX/Ext/Microsoft

Stores Microsoft-specific parameters.

ACCESS/XXX/Ext/Microsoft/ReadOnly

This parameter determines whether users are able to modify settings affected by the Access configuration service provider. Permitted values are 0 for false and 1 for true. If the value is set to 1, users will be able to view, but not change, the Access settings on the device.

The following table shows the default settings.

Permissions

Read/Write

Data type

Boolean

Roles allowed to query and update setting

Manager

Operator TPS

ACCESS/ XXX /Ports

Specifies the port numbers associated with the parent metanetwork.

The following table shows the default settings.

Data Type

Node

Roles allowed to query and update setting

Manager

AuthenticatedUser

ACCESS/ XXX /Ports/PortNbr XXX

Specifies a single port number associated with the grandparent metanetwork. PortNbr XXXis a numbered field beginning at zero, so if you have two port numbers associated with a metanetwork, you would use PortNbr0 and PortNbr1 to specify the port numbers.

The following table shows the default settings.

Data Type

String

Roles allowed to query and update setting

Manager

AuthenticatedUser

See Also