Scheduled PAM heartbeats failing
Hello,
The automated scheduled PAM heartbeats for Domain User type entries seem to be failing, even though initiating a manual heartbeat succeeds.
Entry is set to inherit lifecycle from vault root, which is set to custom\Default.
Default lifecycle policy heartbeat schedule set to Default (custom).
Default (custom) Heartbeat schedule set to once per day in PAM system settings.
Please let me know any additional information is required.
Thanks
Joe
254b30e6-653e-444e-860e-714236d9d51a.png
15240bd8-2d98-4327-943a-1add6597e013.png
6bcd1574-0870-41f0-bb30-c87d183b7b78.png
15251c83-00ec-4eb9-85ed-bc5f9f4154db.png
871aa019-42cc-4f09-9fd5-9db532fefaca.png
94d54336-fef2-4878-9e85-0052aaa87599.png
All Comments (4)
Hello Joe,
We are currently investigating the issue.
In the meantime, could you please verify which version of the PAM Service is installed on your system? If you are not already running the latest version, please update to the most recent release and let us know the outcome.
Additionally, could you provide the PAM Service logs for further analysis?
Thank you for your cooperation.
Kind regards,
Sayed
pam-service.png
Hi Sayed,
Thanks for your assistance with this. The Hub service was updated to latest version on Friday, and it appears the scheduled heartbeats are still failing. Can you send me a file upload link to provide the log please?
There are errors present saying:
1) '[Error] - Could not connect to Provider', however manually testing the PAM provider is successful.
2) 'Unable to find PAM provider with id <GUID> in vault <GUID>: 403. Trying in global vault.'
Thanks
Joe
Hi Joe,
I’m pleased to let you know that we were able to reproduce the issue, and a fix has been implemented. The fix will be included in the next PAM Service release, which is expected to be available soon.
Best regards,
Sayed
Sounds good, thanks for the update Sayed
