Problem Note 69506: Creating a credential in a token domain returns the error "Access token request failed"
In a multi-tenant environment, the following error is returned when a service account creates a credential in a token domain and assigns it to a user identity:
Access token request failed; user: user-Id, scope: n/a, response:
401:invalid_token.
Token bears a non-existent user ID: 46775d35-9ebd-4e26-94f5-
f2ce34df5850
traceId: 19a93082b45c4444
path: /credentials/domains/token-domainId/users/user-Id
A similar error occurs if it is assigned to a group identity.
The credentials microservice log does not show any activity when this error occurs.
Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.
Verify That the Update Is Installed
Confirm that sas-credentials, sas-saslogon, and sas-identities services are at build versions 1.39.3, 2.53.15, and 2.56.7 or later, respectively. To do so, use one of the methods shown here:
-
Run the following rpm commands from the SAS Viya microservices host machine:
rpm -q sas-credentials​
rpm -q sas-saslogon
rpm -q sas-identities
-
The version number is shown after the service name. Here are examples:
sas-credentials-1.39.3-20220831.1661960478735.x86_64
sas-saslogon-2.53.15-20220826.1661516581052.x86_64
sas-identities-2.18.10-20191027.1572205929619.x86_64
- Connect to credentials/apiMeta and SASLogon/apiMeta endpoints. The XML output shows the version in this way:
"buildVersion":"1.39.3"
"buildVersion":"2.53.15"
"buildVersion":"2.18.10"
Operating System and Release Information
SAS System | SAS Viya | Microsoft Windows Server 2012 R2 Datacenter | 3.5 | 3.5 | Viya | Viya |
Microsoft Windows Server 2012 R2 Std | 3.5 | 3.5 | Viya | Viya |
Microsoft Windows Server 2016 | 3.5 | 3.5 | Viya | Viya |
Microsoft Windows Server 2019 | 3.5 | 3.5 | Viya | 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.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-03-15 14:22:40 |
Date Created: | 2022-08-26 20:28:51 |