Why is a user unable to login to the TIBCO Data Virtualization Studio using the OAuth Azure domain authentication?
Article ID: KB0071089
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | TIBCO Data Virtualization 8.7 |
Description
When a user attempts a login to the TDV Studio using the OAuth Azure domain the following error is seen:
===
ERROR [jetty thread pool-140] Util - User Exception Occurred
com.compositesw.common.UserException: Unsupported token type.
An internal error occurred while processing the request. Cause: Parsing JWT token error. [Log ID: 32080c11-f19f-42ed-83a6-b129612dd90b]
===
The OAuth domain has already been configured in the Web manager without any issues and the login to Azure is successful as well.
===
ERROR [jetty thread pool-140] Util - User Exception Occurred
com.compositesw.common.UserException: Unsupported token type.
An internal error occurred while processing the request. Cause: Parsing JWT token error. [Log ID: 32080c11-f19f-42ed-83a6-b129612dd90b]
===
The OAuth domain has already been configured in the Web manager without any issues and the login to Azure is successful as well.
Issue/Introduction
This article will share the configuration change that needs to be done to allow a user to login to the TIBCO Data Virtualization Studio using the OAuth domain.
Resolution
In the manifest file for the application registered in Azure, the following line needs to be modified:
accessTokenAcceptedVersion:2
Note: By default, this value is set to 'null' in the manifest file.
The accessTokenAcceptedVersion value is set to 2 so that the issuer will become
accessTokenAcceptedVersion:2
Note: By default, this value is set to 'null' in the manifest file.
The accessTokenAcceptedVersion value is set to 2 so that the issuer will become
login.microsoft.com instead of sts.windows.net.
Additional Information
https://stackoverflow.com/questions/68703227/jwt-validation-sts-windows-net-vs-login-windows-net-why-are-the-issuers-not-c
Feedback
Yes
No
Powered by
