Dynamics plugins SECURE/UNSECURE CONFIGURATION VARIABLES

 

• Secure Configuration 
• Unsecure Configuration 

 

The Microsoft Dynamics CRM platform supports an optional plug-in constructor that accepts either one or two string parameters. If you write a constructor like this, you can pass any strings of information to the plug-in at run time.  

 

The following sample shows the format of the constructor. In this example, the plug-in class is named SamplePlugin. 

 

The first string parameter of the constructor contains public (unsecure) information. The second string parameter contains non-public (secure) information.  

 

Secure refers to an encrypted value while unsecure is an unencrypted value. 

Secure Configuration	Unsecure Configuration
Not solution aware, so it will have to be configures for each environment	Is solution-aware, so it will be automatically transported with the plugin step
Step specific i.e., needs to be provided for each step	Step specific i.e., needs to be provided for each step
Configuration data can be secured as any other entity using CRM Security model.    Configuration data is stored in a separate entity  ‘SDKMessageProcessingStepSecureConfiguration’	Configuration is just an attribute in the plugin step so you can’t control privileges