The JSON Web Key (JWK) served by SASLogon/token_key has changed in SAS^® Viya^® Stable 2024.12 to include the x5c parameter as outlined in RFC 7517. The x5c parameter is not parsed correctly by SAS^® 9.4 and SAS^® Viya^® 3.5 clients. SAS code that establishes connections that rely on OAuth Tokens issued by SAS Logon Manager to connect from SAS 9.4 or SAS Viya 3.5 to SAS Viya Stable 2024.12 and later fail with the following error:

This issue affects all versions of SAS^®9 and SAS Viya 3.x that connect to any SAS Viya platform deployment on Stable 2024.12 or later.

This issue most commonly affects connections from SAS 9.4 or SAS Viya 3.5 to SAS^® Cloud Analytic Services on the SAS Viya platform. However, it can also affect SAS code that uses the SAS_VIYA_TOKEN Environment Variable to establish a connection to the SAS Viya platform.

Currently, there is no workaround for this issue.

SAS recommends that customers who rely on connections between SAS 9.4 or SAS Viya 3.5 to their SAS Viya platform avoid updating their SAS Viya platform version to Stable 2024.12 or later until they install the fix on their SAS 9.4 or SAS Viya 3.5 deployment.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M8 is available at:

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M7 is available at: