JWP crashes when a user doesn't exist in Cyberark
search cancel

JWP crashes when a user doesn't exist in Cyberark

book

Article ID: 423258

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When a LOGIN object contains a user whose password is set to be checked against Cyberark (Password Vault=Cyberark), doesn't exists in Cyberark, the JWP displays the following error:

20251121/095950.913 - 11426  U00045014 Exception 'java.lang.IllegalArgumentException: "unable to read credentials from https://cyberark.<server>/AIMWebService/api/Accounts?UserName=<user>&AppID=Automic&Safe=<Safe>&Reason=Automic+Batch, return code: 404"' in 'com.automic.cyberark.backend.HttpRequestExecutor.getPassword():75'.

In some environments, the JWP crashes. In that case, as a knock on effect, WP processes may also crash with the following message:

Runtime exception: : No such file or directory
<EOF>

Cause

User doesn't exist in Cyberark

Resolution

Create the user in Cyberark 

Additional Information

If the crash can be reproduced while running a trace (tcp/ip=2,db=4), please open a support case for Broadcom to investigate further.