New A2A Client Will Not Register

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

A new A2A client has been installed, but does not register in PAM. The new A2A client login can be seen in the Tomcat log, but the device is not listed in PAM.

2025-11-28T17:19:36.018+0000 INFO [TP7] com.cloakware.cspm.server.app.impl.RegisterRequestServerCmd.validateParameters RegisterRequestServerCmd.validateParameters hostname:new-a2a.example.com, ip:10.#.#.85, port:28888, version:4.12.3, clientType:java osName:Windows Server 2019, osVersion:10.0, osArch:amd64 fipsEnabled:true clientToken:##### fingerprint:##### nodeIdXML:<?xml version="1.0" encoding="utf-8" ?><nodeid><macaddr>#####</macaddr><machineid>#####</machineid><applicationtype>cspm</applicationtype></nodeid>
2025-11-28T17:19:36.336+0000 INFO [TP7] com.cloakware.cspm.server.app.impl.ClientLoginCmd.validateParameters ClientLogin.validateParameters hostname:new-a2a.example.com, ip:10.#.#.85, port:28888, version:4.12.3, clientType:java osName:Windows Server 2019, osVersion:10.0, osArch:amd64 fipsEnabled:true clientToken:##### fingerprint:##### nodeIdXML:<?xml version="1.0" encoding="utf-8" ?><nodeid><macaddr>#####</macaddr><machineid>#####</machineid><applicationtype>cspm</applicationtype></nodeid>

Cause

Searching for the IP address in the Devices page showed that the IP address used by the new A2A client was reused by a decommissioned server which was previously managed by PAM.

Resolution

Delete the decommissioned server from PAM and restart the A2A agent to complete the registration.

Additional Information

It is possible that there is a decommissioned device which uses that IP, but is stored in PAM through the FQDN. If that is the case, then do a DNS search for the IP address and if it resolves to an older hostname, search for that in the Devices page.