search cancel

A2A scripts created for a request server disappear from the GUI


Article ID: 254307


Updated On:


CA Privileged Access Manager (PAM)


Sometimes a situation arises where for an apparently correctly registered A2A client, any new script being registered immediately disappears from the GUI. This happens even though PAM shows there is communication to the machine, and there are no errors reported anywhere.


CA PAM several releases


This is due to the Request_serverID field for the host we are considering, as defined in the host table in the uag access database in PAM missing the reference to its requestserverid entry in the requestserver in the cspm database. For a successful A2A client to work, you need to reference its requestserver table entry in the host access table, so the Request_serverID entry there needs to reference the corresponding requestserverid value in the cspm database.

There is a number of reasons why this may have happened, including for instance deleting duplicate entries in the GUI or registration errors.



Correcting this error requires recreating the requestserver (delete all entries for it from the PAM GUI and restart A2A client so that it registers itself again) or opening a ticket with Broadcom Support for them to take the necessary corrective actions in the database.