Autoping Fails When Using Custom Encryption Key (encryption_type=AES)

Products

• CA Workload Automation AE - Business Agents (AutoSys)
• CA Workload Automation AE - Scheduler (AutoSys)
• Workload Automation Agent

Issue/Introduction

Autoping to a Workload Automation AE (WAAE) agent fails when the machine definition is configured with encryption_type: AES and a custom key_to_agent attribute.

Note: If the encryption_type is set to DEFAULT, autoping succeeds.

Environment

AutoSys Workload Automation: All version

Cause

The cryptkey.txt file located on the agent machine is invalid or mismatched with the custom encryption key specified in the WAAE machine definition.

You can verify this by examining the receiver.log file in the <AGENT_INSTALL>/log/ directory. The log will contain the following error when a message arrives from the WAAE Scheduler/App Server:

cybermation.library.communications.CybConversationException: Bad padding

Resolution

Option 1: Copy from a working agent

If you have another agent in the same environment using the same custom encryption key that is currently working, you can synchronize the keys:

1. Navigate to the directory containing the working cryptkey.txt file.
2. Copy the cryptkey.txt file in binary mode to the same location on the failing agent machine.
3. Restart the agent service on the failing machine.

Option 2: Generate a new key

If you do not have another agent with a functional key, you must recreate the cryptkey.txt file:

1. Use the as_config utility located on the WAAE server to generate the key for the custom encryption value. (Refer to WAAE online documentation for specific as_config syntax and usage).
2. Place the generated cryptkey.txt file into the appropriate directory on the failing agent machine.
3. Restart the agent service on the failing machine.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region."