Usage Note 66148: Details about the encryption algorithm that is logged to the SAS® Object Spawner log when connecting to a SAS® Viya® workspace server
When a client application such as SAS® Enterprise Guide® 8.2 connects to a SAS Viya workspace server, the initial connection attempt is logged as a failure with SAS Proprietary as the encryption algorithm used. The initial failed attempt results in error messages being written to the object spawner log similar to the following:
Secure communications error status 807ff03c description "::ffff:1.2.3.4: The data received is not a valid SSL/TLS packet."
Secure communications error status 807ff03c description "::ffff:1.2.3.4: The data received is not a valid SSL/TLS packet."
Bridge Protocol Engine Socket Access Method was unable to complete the SSL related communication due to an error.
New client connection (5) accepted from server port 8591 for user sas. Encryption level is Everything using encryption algorithm SASPROPRIETARY. Peer IP address and port are [::ffff:1.2.3.4]:57262 for APPNAME=SAS Enterprise Guide.
This failed connection notifies the client that the server connection requires SSL/TLS. The client then re-establishes the connection using SSL/TLS, which meets the servers requirement and connects the client to the workspace server.
Submitting the following to the connected workspace server lists NETENCRYPTALGORITHM=(SSL AES) as the algorithms specified when the server is started. NETENCRYPTALGORITHM specifies the algorithm or algorithms to be used for encrypted client/server data transfers.
proc options option=netencryptalgorithm;run;
Operating System and Release Information
| SAS System | SAS Integration Technologies | Linux for x64 | 9.4_M6 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2019 | 9.4_M6 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2016 | 9.4_M6 | | 9.4 TS1M6 | |
| Microsoft Windows Server 2012 R2 Std | 9.4_M6 | | 9.4 TS1M6 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Date Modified: | 2022-04-28 15:54:53 |
| Date Created: | 2020-06-17 15:44:27 |