azuredatastudio-postgresql is an extension for Azure Data Studio that enables you to work with PostgreSQL databases
Other
195
stars
37
forks
source link
FATAL: The access token does not have a valid audience claim. Please acquire a new token for the resource "https://ossrdbms-aad.database.windows.net". #505
Describe the bug
When connecting to an Azure Postgres Flexible Server, the connection errors out with:
FATAL: The access token does not have a valid audience claim. Please acquire a new token for the resource "https://ossrdbms-aad.database.windows.net".
To Reproduce
Steps to reproduce the behavior:
Create a new Connection to an Azure Postgres Flexible Server
Use Azure Active Directory authentication
Expected behavior
No error, connection succeeds
Desktop (please complete the following information):
OS: Windows Server 2022
ADS (please complete the following information):
Version: 1.48.1 (system setup)
Commit: 8825ec21e67a34ede00e4f02a4afc692eb6cab61
Date: 2024-06-13T21:07:19.253Z
VS Code: 1.82.0
Electron: 25.9.8
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.20348
We have found a workaround for this, it seems like this is caused by an old token.
After deleting the token cache in %appdata%\azuredatastudio\Azure Accounts, things started to work again.
Describe the bug When connecting to an Azure Postgres Flexible Server, the connection errors out with: FATAL: The access token does not have a valid audience claim. Please acquire a new token for the resource "https://ossrdbms-aad.database.windows.net".
To Reproduce Steps to reproduce the behavior:
Expected behavior No error, connection succeeds
Desktop (please complete the following information):
ADS (please complete the following information): Version: 1.48.1 (system setup) Commit: 8825ec21e67a34ede00e4f02a4afc692eb6cab61 Date: 2024-06-13T21:07:19.253Z VS Code: 1.82.0 Electron: 25.9.8 Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Windows_NT x64 10.0.20348
Postgres Extension: 0.6 Azure Postgres v14/v15
Same issue reported here: https://github.com/microsoft/azuredatastudio/issues/25671
@nasc17 Is this project still active?