Special Characters in Certificate Password Cause Agent Install to Fail
search cancel

Special Characters in Certificate Password Cause Agent Install to Fail

book

Article ID: 383342

calendar_today

Updated On:

Products

CA Process Automation Base Process Automation Manager

Issue/Introduction

When installing the ITPAM Agent (using SSL), the following error appears:

"Error while trying to connect to domain server or generating keystore."

Steps to replicate the issue

  1. Install ITPAM 4.4 with Secure Communication selected and a password containing the "&" special character.  The installation completes successfully and the Orchestrator can be accessed in the normal way.

  2. Login to the Domain Orchestrator on a remote server for agent installation.  Select Configuration - Installation and click to the Agent Install button.  The agent installer begins as usual.

  3. When prompted for the Certificate Password we provide the same password used in step 1 above.  The installer fails with incorrect password message. 

  4. Remove the Orchestrator Installation and install again with a password containing only letters and numbers

  5. Remove all files from the folder C:\Users\Administrator\AppData\Local\Temp\2 on the Agent Server

  6. Rerun the Agent installation and this time with the password abcdef the Agent installs correct.

The same happens when you use a "ยง" character in the password.

The problem was first discovered with ITPAM 4.4 CP03, but could exist in other earler versions as well.

Environment

IT Process Automation 4.4.x

Cause

Problem is using the Special character like "abc&def" for the "CERTPASSWORD" while installing the Orchestrator and when we install the Agent we need to enter this "CERTPASSWORD" to ensure agent is trusted to install. Here the problem is, when an agent is installing, it will send the request to the server to verify the  cert password as a path parameter. The following are the not valid path parameters and which is causing the issue. 

&, ?, =, /, or #

Resolution

A fix was provided which can handle the passwords with special characters. The final fix will be available in the upcoming CP (PAM 4.4 CP04)