PAM Access Sessions Fail When Using PVPs Created Through the CLI

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

A password view policy was created in PAM through the remote CLI using the required parameters mentioned in the addPasswordViewPolicy CLI documentation page. When that PVP is assigned to a target account, SSH or RDP connections with that target account do not work. PVPs created through the UI do not have this issue.

Environment

Privileged Access Manager 4.2.0 - 4.2.2

Cause

The issue will occur if the PVP has either "Re-Authenticate For Auto Connect" or "Reason Required For Auto Connect" enabled. When created through the CLI, some of the optional attributes related to the Service Desk integration do not get set. These missing attributes cause the auto-connect to fail.

Resolution

The defect has been fixed in the 4.2.3 and 4.3.0 releases, upgrade to resolve the issue.