PAM Scheduled Reports Stopped Being Emailed

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

PAM has scheduled reports configured to run every day and email a list of recipients. Recently, the emails from the report stopped being received. In the Tomcat logs, the following error is observed when the report was scheduled to run.

Mar 20, 2023 7:11:00 PM com.cloakware.cspm.server.app.impl.ScheduledReportCmd invoke
WARNING: Couldn't send email: 
com.cloakware.cspm.server.app.ApplicationException: CommandSequenceCmd.getUser: get user failed
    at com.cloakware.cspm.server.app.impl.CommandSequenceCmd.getUser(CommandSequenceCmd.java:419)
    at com.cloakware.cspm.server.app.impl.ScheduledReportCmd.getUsers(ScheduledReportCmd.java:152)
    at com.cloakware.cspm.server.app.impl.ScheduledReportCmd.invoke(ScheduledReportCmd.java:115)
    at com.cloakware.cspm.server.app.impl.ApplicationContextImpl.invokeCommand(ApplicationContextImpl.java:276)
    at com.cloakware.cspm.server.app.impl.ApplicationContextImpl.invokeCommand(ApplicationContextImpl.java:124)
    at com.cloakware.cspm.server.app.impl.ApplicationContextImpl.invokeCommand(ApplicationContextImpl.java:116)
    at com.cloakware.cspm.server.app.impl.ApplicationContextImpl.invokeCommand(ApplicationContextImpl.java:112)
    at com.cloakware.cspm.server.security.ScheduledJob.execute(ScheduledJob.java:90)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

Environment

Privileged Access Manager, 4.0.x and 4.1.0-4.1.2

Cause

A user was deleted from PAM, but they remained listed as an email recipient for the scheduled reports due to an issue within the code. Since the user could not be found when the scheduled report went through the list of email recipients, the report errored out.

Resolution

The issue is resolved in 4.1.3 as DE561745. As a workaround, one can open the scheduled report and confirm the list of email recipients is correct, then click OK to save the report. This will modify the database and correct the data for the scheduled job.

Additional Information

DE561745 can be found in the list of resolved issues for 4.1.3 in the link below.

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/privileged-access-manager/4-1-3/release-information/Resolved-Issues-in-4-1-3.html