AEWS does not respond and waae_webservices.log has repeating message org.bouncycastle.crypto.fips.FipsUnapprovedOperationError: password must be at least 112 bits
search cancel

AEWS does not respond and waae_webservices.log has repeating message org.bouncycastle.crypto.fips.FipsUnapprovedOperationError: password must be at least 112 bits

book

Article ID: 397039

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

AutoSys Rest WebServices (AEWS) component does not respond to browser or curl requests, they just timeout eventually.

$AUTOUSER/out/waae_webservices.log has repeating messages like this:

INFO   | jvm 1    | 2025/05/08 08:49:30 | [EL Severe]: ejb: 2025-05-08 08:49:30.601--ServerSession(711931399)--org.bouncycastle.crypto.fips.FipsUnapprovedOperationError: password must be at least 112 bits
INFO   | jvm 1    | 2025/05/08 08:49:30 | [EL Severe]: ejb: 2025-05-08 08:49:30.626--ServerSession(711931399)--org.bouncycastle.crypto.fips.FipsUnapprovedOperationError: password must be at least 112 bits

 

Environment

Workload Automation AutoSys

Cause

$JAVA_HOME/lib/security/java.security file was modified by customer to have an extra line like this:

security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider

 

This was somehow interfering with the interaction of AEWS with the database connection / retrieving the SSL certificate that AutoSys stores in its database.

 

 

Resolution

  • Restore the original $JAVA_HOME/lib/security/java.security file that did not have the line "security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider"  in it
  • Restart the AEWS server