search cancel

Rest API stopped working after update to 4.1

book

Article ID: 243092

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

After the upgrade to 4.1 all the API integrations we use stopped working:

every API response body is empty (response code is 200), whether the object requested (in case of a GET request for example) exists or not.

The same problem is found both by calling the API through PAM's API DOC portal and with powershell. Calling the API through PAM's API DOC shows the Response Body as 'no content'.

 

Cause

A code change in 4.1 had a bug that caused this problem when an API key was not used for more than 24 hrs, which is why it was not noticed by QA during release testing.

Environment

Release : 4.1

Component : PRIVILEGED ACCESS MANAGEMENT

Resolution

Published hotfix 4.1.0.02, available for download from the PAM Solutions & Patches page. Hotfix release notes are attached here.

Attachments

1654263218487__PAM_4.1.0.02_Hotfix_Release_Notes.pdf get_app