Custom Connector failing when attempting to call information on second Master Account.

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

We have a custom connector use case where update of a target account requires two other accounts, a logon account and a master account. PAM allows definition of multiple master accounts, and they are supposedly added to the "masterAccounts" list, but on the customer connector side only the first account can be retrieved.

Environment

Release : 3.4-3.4.5, 4.0.0-4.0.1

Component : PRIVILEGED ACCESS MANAGEMENT

Cause

This is a limitation of the initial custom connector framework implementation

Resolution

This problem will be fixed in 3.4.6 and future releases, including the next 4.0 maintenance release 4.0.2.