The SAS Object Spawner fails to start with "The object spawner is running in FIPS mode... Unable to initiate IOM run-time"


When you configure the SAS Object Spawner to use TLS to encrypt IOM communication and FIPS compliance enforcement is enabled (the ENCRYPTFIPS system option), the SAS Object Spawner might fail to start with the following error message:

The object spawner is running in FIPS compliance mode, therefore the only encryption algorithm that is supported for the Operator connection for object-spawner-name (object-spawner-metadata-id) is AES.

CLASSFACTORY cannot be instantiated.

Unable to initiate the IOM run-time.

This issue occurs because the ENCRYPTFIPS option does not consider the "SSL" NETENCRYPTIONALGORITHM option as valid for FIPS compliance.