AutoSys WebService calls fail with "Unrecognized field" error in version 24.1

Products

• Autosys Workload Automation

Issue/Introduction

AutoSys Web Server (AEWS) calls in version 24.1 fail with syntax errors, whereas the same calls worked successfully in older AutoSys versions.

Example Error: When executing a curl command to start a job:

Bash

 

curl -X POST "https://example.com:9443/AEWS/event/start-job" \
-H "accept: */*" \
-H "Content-Type: application/json" \
-d "{\"jobName\":\"test123\",\"comment\":\"this is a comment\",\"startAutoSysJob\":\"test\"}" \
--user username:password -k

The response returns the following error:

Plaintext

 

Unrecognized field "startAutoSysJob" (class com.ca.waae.wsquery.WsEvent), not marked as ignorable (17 known properties: "response", "priority", "quePriority", "eventTime", "jobName", "xInstName", "stopFlag", "jobStatus", "application", "alarm", "action", "stepName", "comment", "machine", "signal", "gvarValue", "group"])
 at [Source: REDACTED (StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION disabled); line: 1, column: 72] (through reference chain: com.ca.waae.wsquery.WsEvent["startAutoSysJob"])

 

Resolution

In AutoSys versions prior to 24.1, the AEWS component allowed additional or unexpected value pairs in the JSON payload even if they were not documented or valid.

As of AutoSys version 24.1, the web service has been updated for improved security and strict validation. If a request contains any unknown, unexpected, or incorrect fields, it will be rejected.

In the provided example, startAutoSysJob is not a documented or expected value for the WsEvent class, which causes the call to fail in AutoSys 24.1.x.

Action Required:

1. Review the JSON payload used in the WebService call.

2. Remove any fields that are not part of the documented AEWS API specification.

3. Ensure only the 17 known properties listed in the error message (e.g., jobName, comment, priority, etc.) are used where appropriate.

Additional Information:

This change in behavior is intentional and represents a more secure approach to handling API requests by preventing the processing of unexpected data.

---