Autosys production WCC primary URL not started, WCC services properly started but URL is not up.

Products

• Autosys Workload Automation

Issue/Introduction

Our Windows server team Patch the WCC machine.
After the patching, the WCC can not be accessed through the URL, though the services do start.
We tried rolling back the changes the OS did but that did not resolve the issue.

We are seeing the below errors in the WCC logs

Error 1:
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 | @asi <ForkJoinPool-90-worker-1> [] ERROR #CAMResponseLoader                  # Failed request with exception : https://<HOSTNAME>:9443/AEWS/machine?version=2&filter=createStamp%3C0 , Unexpected exception connecting to <HOSTNAME>: <Attempt to create key pair with unapproved RNG: EC> 
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 | @asi <ForkJoinPool-90-worker-1> [] ERROR #CAMResponseLoader                  # All requests failed.
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 | @asi <ForkJoinPool-90-worker-1> [] ERROR #CAMResponseLoader                  # All requests failed.

Error 2:
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 | Caused by: com.ca.workload.services.exceptions.WlaInternalServerErrorException: Unexpected exception connecting to <HOSTNAME>: <Attempt to create key pair with unapproved RNG: EC>
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 |     at com.ca.workload.services.exceptions.WlaException.convertProcessingException(WlaException.java:57)
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 |     at com.ca.workload.services.config.CAMResponseLoader.getResponse(CAMResponseLoader.java:291)
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 |     at com.ca.workload.services.config.CAMResponseLoader.getResponse(CAMResponseLoader.java:131)
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 |     at com.ca.workload.services.cam.adapters.AEAdapter.getAgents(AEAdapter.java:155)
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 |     ... 7 more
INFO   | jvm 1    | 2024/02/24 17:41:14 |     5111 | Caused by: org.bouncycastle.crypto.fips.FipsUnapprovedOperationError: Attempt to create key pair with unapproved RNG: EC

Environment

Autosys 12.x
WCC 12.x

Cause

Java Security file was improperly renamed

Resolution

The root cause of the problem:
 improperly renamed the <WCC>/JRE_WA/bin/java/lib/security/ file
From:
java.security
To:
java.security.security

Resolution:
Rename the file back to its original format.
java.security