Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connecting between Client and Server through SSH tunnel in CMD



User needs to test if the connection between the Chordiant Marketing Director (CMD) Client and the CMD server works through an SSH Tunnel.

User would also like to know if CMD uses any encryption between client and server communications.

Error Messages

Not Applicable

Steps to Reproduce

Not Applicable

Root Cause

Not Applicable


The architecture of Marketing Director (MD) has been designed in such a way that the MD client and the MD application server communicate through the use of Remote Procedure Calls (or RPC).

In order to cope in the most efficient way with multiple instances of MD client, whenever a user connects to the application, an RPC process is spawned. When the user logs out of the application, this process ceases.

Hence, the communications between the client and server cannot be tunnelled via SSH.

Autonomic Event Services (AES) standard algorithm is used in MD for encryption or decryption of password, and is available both at client and server side.

Published March 16, 2017 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us