We have a customer who's A2A Client is trying to pull the credential for their job, and it is pulling an old credential but giving a 400 success code. We checked on our end and it is not showing up as a client request in failed or successful, the request is not showing at all. Even in the logs we are not seeing anything. Nothing has changed for the script in the week that would make it different, its still pulling last week's credential after a recycle. User is unable to run their tower job.
This issue started after an upgrade of the PAM server from 3.4.5 to 4.0
Release : 3.4
Component : PRIVILEGED ACCESS MANAGEMENT
Stop the A2A client
then Start the A2A client
This caused the A2A client to get a fresh connection to PAM appliance