Static VARA cannot be modified via REST API if the root folder of its path is not accessible to the submitting user
search cancel

Static VARA cannot be modified via REST API if the root folder of its path is not accessible to the submitting user

book

Article ID: 277552

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

A problem that did not exist in prior AE version 21 was detected in version 21.0.7

The problem was also reproduced in 21.0.8
A REST jobs tries to access and to modify a VARA 'XXX.XXX.VARA' in the folder '/<FOLDER1>/<FOLDER2>/<FOLDER3>/'
The submitting user '<USER1<' has fulll access rights to ''\<FOLDER1>\<FOLDER2>\<FOLDER3>\*' and ''\<FOLDER1>\<FOLDER2>*' but nothing for ''\<FOLDER1>*"'.

The response of the aborted job execution will reports an access denied failure.

Sending request...
Response:
Status:403 Forbidden
Response headers:[Date:[Wed, 25 Oct 2023 14:35:43 GMT], Content-Type:[application/json], Content-Length:[135]]


An error occurred - after the request
Response error code: 403 (Response family:CLIENT_ERROR), Exception: {
  "code" : 9,
  "error" : "''\\\<FOLDER1>\\\<FOLDER2>\\\<FOLDER3>'': Access denied",
  "details" : "No detail information available."
}:Forbidden

Environment

AE/AWI 21.0.8, RA core 21.0.4, with RA solution 4.6.6

Cause

This is a defect of the Automation Engine detected in version 21.0.8

Resolution

Resolution:

This bug is fixed in the Automation Engine version 21.0.9

Bug Description: A problem has been fixed where objects could not be modified via REST API if the root folder of its path was not accessible to the user performing the modification

Additional Information

Bug ID: AE-34418
Bug Title: Static VARA cannot be modified via REST API if the root folder of its path is not accessible