PAM SC Devices not showing in default groups

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

When deploying PAM Server Control (PAM SC) endpoints to a Utility Appliance (UTA), endpoints may fail to automatically join their preconfigured default groups (e.g., "All Linux Hosts" or "RHEL 7"). Although the heartbeat from the endpoint confirms PAM SC is installed and communicating with the UTA, the device remains outside the intended management groups.

Environment

• CA Privileged Access Manager (PAM) 4.2.1, 4.3.0, 4.3.1
• PAM Utility Appliance (UTA)
• PAM SC Endpoints (e.g., Redhat 7.0 Linux)

Cause

This issue is caused by a product defect (DE668286) where the Utility Appliance does not correctly process the group assignment during the initial onboarding or heartbeat if the device already existed in the database prior to PAM SC deployment.

Resolution

Fixed in release 4.3.2 and higher. 

Additional Information

If an immediate upgrade is not possible, contact Broadcom Support to request the hotfix related to defect DE668286.