Overview of security metadata

The Dynamics Security Service controls access to service methods. To secure a new service, create a "security helper" application that adds security metadata for the new service methods. Use the "security helper" application to add the following types of metadata.

• Add a Dynamics Security Service operation for each method in your service. An operation is a specific action that the Dynamics Security Service secures.
• Add Dynamics Security Service tasks for your service. A task is a collection of related operations. Use tasks to simplify the administration of security for your service.
• Add operations and tasks to Dynamics Security Service roles. To provide administrative access to your service, assign your security operations to the Dynamics Security Service Superuser role.

To update the Dynamics Security Service, your "security helper" application requires configuration parameters from the Web Services for Microsoft Dynamics GP installation. One way to retrieve the required parameters is to import the contents of an existing Dynamics GP Service configuration file into the configuration file of your "security helper" application. The code for the sample Leads service "security helper" application demonstrates one technique for importing the required configuration information.

When you uninstall your service, you should also remove the security metadata associated with your service from the Dynamics Security Service. To remove your security metadata, add code to your "security helper" application that removes the security operations and tasks that you created. The "security helper" application for the sample Leads service shows how to remove security metadata from the Dynamics Security Service.