EngageOne Designer - setting up Secure data transfer in a Client/Server environment

Product Feature: Designer Secure Data Transfer
 
It is possible to set up secure data transfer in EngageOne Designer when installed in a client\server environment.  This is achieved via .NET Remoting which encrypts the communication using Security Support Provider Interface (SSPI)

This is covered in the Installation Guide in the following section (located in the Installing and Configuring Designer section):

Securing data transfer in a Client/Server environment

To ensure client/server data is securely transferred you can configure all data communications to use secure channels. This mode of data transfer contains a set of security protocols that provide identity authentication and secure communication through encryption. To activate this method of data transfer you will need to modify the following files:

• BusObj.config on the server machine
• Processor.dll.config on all client machines.
• ResourceAccessService.exe.config on all client machines

Note: by default these configuration files are shipped with Secure Channel deactivated.

To implement secure channel data communications:

1. For 64 bit Windows, on the server machine use the following path to locate the BusObj.config file: C:\Program Files (x86)\PBBI CCM\DOC1\Designer\Server\.  For 32 bit Windows: C:\Program Files\PBBI CCM\DOC1\Designer\Server\
2. Edit the BusObj.config file using a text editor such as notepad and ensure that the channel tag's secure attribute is set to true, as shown in the code snippet below:

<system.runtime.remoting>
<customErrors mode="off"/>
<application>
<channels>
<channel ref="tcp" secure="true" port="37719">
<serverProviders>
<formatter ref="binary" />
</serverProviders>
</channel>
</channels>

3. For 64 bit Windows, on the client machine(s) use the following path to locate the Processor.dll.config file: C:\Program Files (x86)\PBBI CCM\DOC1\Designer\Client\.  For 32 bit Windows:C:\Program Files\PBBI CCM\DOC1\Designer\Client\
4. Edit the Processor.dll.config file using a text editor and ensure that the channel tag's secure attribute is set to true,as shown below:

<configuration>
<system.runtime.remoting>
<application>
<channels>
<channel ref="tcp" secure="true">
<clientProviders>
<formatter ref="binary" />
</clientProviders>
</channel>
</channels>

5. For 64 bit Windows, on the client machine(s) use the following path to locate the ResourceAccessService.exe.config file: C:\Program Files (x86)\PBBI CCM\DOC1\Resource Access Service\.  For 32 bit Windows: C:\Program Files\PBBI CCM\DOC1\Resource Access Service\
6. Edit ResourceAccessService.exe.config file with a text editor and ensure that the channel tag secure attribute is set to true, as shown below:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
<add key="ResourceServer" value="localhost" />
<add key="ResourceServerPort" value="50241" />
<add key="Protocol" value="tcp" />
<add key="ScratchDir" value="" />
</appSettings>
<system.runtime.remoting>
<application>
<channels>
<channel ref="tcp" port="50242" secure="true">
<serverProviders>
<formatter ref="binary" />
</serverProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
</configuration>

Note: EngageOne® Resource Access Service must be restarted after the ResourceAccessService.exe.config file has been edited.

7. On the server machine restart EngageOne Template Designer Application Service using the Windows Start button, use run to execute services.msc. Locate EngageOne Template Designer Application Service and restart the service.
8. Restart Designer on the client machines.
UPDATED:  May 26, 2020