When a SAS Compute Server session is started, the oAuth token is set in the session after it is initialized. If users of the session are making calls to services, they can use this oAuth token for outgoing calls.

However, if that outgoing call to a service is executed in an autoexec_usermods.sas file, the token is not available. In this scenario, the caller receives the following error:

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

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Viya	Linux for x64	3.5	3.5	Viya	Viya

* 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.

---

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

http://documentation.sas.com/?softwareId=administration&softwareVersion=3.5&softwareContextId=softwareUpdates

---

When you place an outgoing call to a service in the Compute Server autoexec_usermods.sas file, it fails with the error "401: Unauthorized."

Type:	Problem Note
Priority:	medium

Date Modified:	2020-03-16 08:33:32
Date Created:	2020-03-13 15:04:05