Implementing namespace security

After you have developed and tested your custom namespaces, you should secure those namespaces before deploying them in a live production environment. There are two security settings that you need to be concerned about:

Authentication of provisioning requests

There are two type of provisioning requests:

For security reasons, untrusted requests are the standard approach for invoking Microsoft Provisioning Framework for both COM+ and HTTP/SOAP applications.

When testing custom namespaces, you should submit a trusted request that explicitly defines its security context and procedure steps as well as data. Only members of the MPFTrustedUsers group are allowed to submit trusted requests. After testing custom namespaces outside of the production environment, change your namespace coding to secure the namespace by allowing only untrusted requests.

Access to namespace procedures

The default access type of a procedure is public. When deploying a procedure, set the access type to private if public access is not required. By default, the namespace file sets the access type to public to facilitate testing. In a live production environment, this does not provide the appropriate level of security.

During development and testing of namespaces, you can change the Provisioning Manager security settings to grant the AuthenticatedUsers group permissions to submit requests. This will allow you to run private namespaces in the context of any user. For more information, see To grant permissions to submit requests to provisioning engines.


For more information about namespace security, see Maintaining and updating namespaces and procedures and Managing security.