RA Web Service REST 4.6.9 jobs fail with error code 400 Bad Request as headers are not sent

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

The token in the HTTP Request Header of an RA Web Service REST job

 is not passed to the REST endpoint and the job fails with this error:

Response error code: 400 (Response family:CLIENT_ERROR), Exception: { "error" : "Access token was not provided" }:Bad Request

Expected behavior: The WS REST job finishes with:
2023-10-11 15:30:48 pool-2-thread-296: JerseyUtils: Check response code:200
2023-10-11 15:30:48 pool-2-thread-296: JerseyUtils: Response family:SUCCESSFUL

Actual behavior: The WS REST job aborts with:
2023-10-11 15:29:41 pool-2-thread-433: JerseyUtils: Check response code:400
2023-10-11 15:29:41 pool-2-thread-433: JerseyUtils: Response family:CLIENT_ERROR
2023-10-11 15:29:41 pool-2-thread-433: JerseyUtils: Response reason:Bad Request
2023-10-11 15:29:41 pool-2-thread-433: JerseyUtils: Response type:application
2023-10-11 15:29:41 pool-2-thread-433: JerseyUtils: Response error text:

{ "error" : "Access token was not provided" }

Environment

Release: 4.6.9

Component:  RA Web Service REST Solution

Cause

Defect.

Resolution

Workaround:

Use the RA Web Service REST solution 4.6.8.

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): RA Web Service REST Solution 
RA.Web.Service.REST 4.6.10 - Available

Additional Information

Defect ID: RA_WEB_SERVICE_REST-506

Public Short Description: Authentication Header missing in POST requests

Public Description: A problem has been solved where header information is missing in the REST request and response.