Dynamics Plugins

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. 

su1

 

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 

 

su2

su3

 

Advertisement

One thought on “Dynamics plugins SECURE/UNSECURE CONFIGURATION VARIABLES

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s