User account not found in MSAL cache on Linux #23688

cheenamalhotra · 2023-07-07T16:38:44Z

Azure Data Studio Version: 1.44.1
Commit: 8f53a31
Date: 2023-06-01T02:10:44.473Z
OS: Linux x64 6.4.1-arch1-1

I tried unlinking account from Azure Data Studio, removing directories ~/.config/azuredatastudio/Azure Accounts and ~/.config/azuredatastudio/CachedData, and logging back in via private chrome window to ensure there is no cached login, but to no avail, I still get the error when I try to connect.

Any more tips how could I resolve the problem, while waiting for the July release?

Stacktrace:

Microsoft.Data.SqlClient.SqlException (0x80131904): User account '[redacted]@[redacted]' not found in MSAL cache, please add linked account or refresh account credentials.
 ---> System.Exception: User account '[redacted]@[redacted]' not found in MSAL cache, please add linked account or refresh account credentials.
   at Microsoft.SqlTools.Authentication.Authenticator.GetTokenAsync(AuthenticationParams params, CancellationToken cancellationToken) in /_/src/Microsoft.SqlTools.Authentication/Authenticator.cs:line 129
   at Microsoft.SqlTools.Authentication.Sql.AuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters) in /_/src/Microsoft.SqlTools.Authentication/Sql/AuthenticationProvider.cs:line 90
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.<>c__DisplayClass147_1.<<GetFedAuthToken>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OnFedAuthInfo(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.<>c__DisplayClass48_0.<CreateReplaceConnectionContinuation>b__0(Task`1 _)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass30_0.<<OpenAsync>b__0>d.MoveNext() in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 313
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in /_/src/Microsoft.SqlTools.ServiceLayer/Connection/ConnectionService.cs:line 692
ClientConnectionId:[redacted]

1-Azure-Acount-redacted.log

Originally posted by @mishioo and @Anganthier in #23286 (comment)

The text was updated successfully, but these errors were encountered:

github-actions · 2023-07-07T16:41:24Z

We need more info to debug your particular issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

First open the Settings page, find the Mssql: Tracing Level setting and change that to All then restart Azure Data Studio.
Open command palette (Click View -> Command Palette) and run the command Developer: Set Log Level... and set the level to Trace.
Run the repro scenarios.
Collect the following logs:

Console Logs

Open Developer Tools (Help -> Toggle Developer Tools)
Click the Console tab
Click in the log area and select all text (CTRL+A)
Save this text into a file named console.log and attach it to this issue.
Developer Tools can be closed via Help -> Toggle Developer Tools

Application Logs

Open command palette (Click View -> Command Palette)
Run the command: Developer: Open Logs Folder
This will open the log folder locally. Please zip up this folder and attach it to the issue.

Now you can revert the Log/Tracing levels changes made in step 1 and step 2.

cheenamalhotra · 2023-07-07T18:27:06Z

Hi @mishioo and @Anganthier

I was able to reproduce the error on Ubuntu 22 with stable build, and also verified that using Azure Data Studio - Insiders can get you unblocked and resolve the issues, please install the same in the meantime.

This issue will be resolved in the next stable release targeted July, hence closing issue.
Let us know if you continue to face any issues with the insiders build.

Anganthier · 2023-07-08T09:01:05Z

The problem still persists.
I already tried to deleteing .config/azuredatastudio first. Didn't change the outcome. I'll run the trace next.

Version: 1.45.0-insider
Commit: 55b8e3f
Date: 2023-07-06T05:55:20.906Z
VS Code: 1.79.0
Electron: 22.3.14
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Linux x64 5.15.0-76-generic

Microsoft.Data.SqlClient.SqlException (0x80131904): User account '[redacted]' not found in MSAL cache, please add linked account or refresh account credentials.
 ---> System.Exception: User account '[redacted]' not found in MSAL cache, please add linked account or refresh account credentials.
   at Microsoft.SqlTools.Authentication.Authenticator.GetTokenAsync(AuthenticationParams params, CancellationToken cancellationToken) in /_/src/Microsoft.SqlTools.Authentication/Authenticator.cs:line 129
   at Microsoft.SqlTools.Authentication.Sql.AuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters) in /_/src/Microsoft.SqlTools.Authentication/Sql/AuthenticationProvider.cs:line 90
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.<>c__DisplayClass147_1.<<GetFedAuthToken>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OnFedAuthInfo(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.<>c__DisplayClass48_0.<CreateReplaceConnectionContinuation>b__0(Task`1 _)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass30_0.<<OpenAsync>b__0>d.MoveNext() in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 313
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in /_/src/Microsoft.SqlTools.ServiceLayer/Connection/ConnectionService.cs:line 697
ClientConnectionId:1348735a-b3eb-4787-a813-0b759eec489c

Anganthier · 2023-07-08T09:09:49Z

Just saw, that this issue is closed - new ticket or reopen?

cheenamalhotra · 2023-07-08T09:34:36Z

I can re-open the same for investigation - please upload full logs as per above comment.

Anganthier · 2023-07-09T09:05:08Z

As requested:
console.log
20230708T105808.zip

cheenamalhotra · 2023-07-11T07:14:57Z

Hi @Anganthier

The logs are mostly empty other than renderer and it seems like there is a token acquired but it lacks expiry date. To investigate more, can you please enable below logging levels in settings.json file:

"mssql:tracingLevel": "Verbose",
"azure.loggingLevel": "Verbose"

Once you enable these logs - please reload ADS and try reproducing the error again. Please upload logs again with verbose logging.

piyushpaliwal · 2023-07-12T10:40:13Z

I am facing the same issue. Here is the setup I am currently using

Version: 1.46.0-insider
OS: Debian 12

Tried the following

Clear token cache from Azure Data Studio
Remove All saved Accounts
Manually deleting Azure Accounts and CachedData folder inside ~/.config/azuredatastudio

github-actions · 2023-07-13T07:00:09Z

We need more info to debug your Azure Active Directory issue. If you could attach your logs to the issue (ensure no private data is in them), it would help us fix the issue much faster.

In the settings menu, find the setting titled Azure: Logging Level and select the Verbose option
Restart Azure Data Studio
Run the process that produces your error
Open command palette (Click View -> Command Palette)
Run the command: Developer: Open Logs Folder
Follow this path to find the Azure Accounts log file: [default log folder]/exthost1/output_logging_[earliest timestamp]/#-Azure Acounts.log
Please attach the Azure-Accounts.log file to the issue.

cheenamalhotra · 2023-07-13T07:01:07Z

I also tested with latest insiders build on Debian 12 and Ubuntu 22 and I can't repro issue with AAD auth/server logins.

Please upload logs for further investigation.

bard83 · 2023-07-13T12:01:54Z

Moved my comment here.

Same issue also using 1.46-insider.

Below the exception and the logs.

Microsoft.Data.SqlClient.SqlException (0x80131904): User account '*****@*******' not found in MSAL cache, please add linked account or refresh account credentials.
 ---> System.Exception: User account ''*****@*******' not found in MSAL cache, please add linked account or refresh account credentials.
   at Microsoft.SqlTools.Authentication.Authenticator.GetTokenAsync(AuthenticationParams params, CancellationToken cancellationToken) in /_/src/Microsoft.SqlTools.Authentication/Authenticator.cs:line 129
   at Microsoft.SqlTools.Authentication.Sql.AuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters) in /_/src/Microsoft.SqlTools.Authentication/Sql/AuthenticationProvider.cs:line 90
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.<>c__DisplayClass147_1.<<GetFedAuthToken>b__1>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OnFedAuthInfo(SqlFedAuthInfo fedAuthInfo)
   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)
   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
   at Microsoft.Data.ProviderBase.DbConnectionFactory.<>c__DisplayClass48_0.<CreateReplaceConnectionContinuation>b__0(Task`1 _)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass30_0.<<OpenAsync>b__0>d.MoveNext() in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 313
--- End of stack trace from previous location ---
   at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in /_/src/Microsoft.SqlTools.ServiceLayer/Connection/ConnectionService.cs:line 692
ClientConnectionId:0d42e9d9-2cdf-49aa-bb8e-aecc1963f764

1-Azure Accounts.log

cheenamalhotra · 2023-07-13T18:23:42Z

HI @bard83

Could you please attach MSSQL logs as well (instructions above)? There seems to be no error in Azure account logs.

bard83 · 2023-07-13T21:02:57Z

console.log
20230713T224626.zip

cheenamalhotra · 2023-07-13T21:13:49Z

@bard83 I see these errors in exthost.log file btw..

[2023-07-13 22:49:05.925] [exthost] [debug] ProxyResolver#resolveProxy https://login.microsoftonline.com/common/discovery/instance?api-version=1.1&authorization_endpoint=https://login.microsoftonline.com/02dca5ee-e24f-4cee-ab0a-1d1054bebd16/oauth2/v2.0/authorize DIRECT 
Error: Error for stack trace
	at resolveProxy (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:105:69)
	at /usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:294:77
	at new Promise (<anonymous>)
	at _PacProxyAgent.resolveP [as resolver] (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:294:54)
	at _PacProxyAgent.<anonymous> (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:70:37)
	at Generator.next (<anonymous>)
	at /usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:8:71
	at new Promise (<anonymous>)
	at __awaiter (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:4:12)
	at _PacProxyAgent.callback (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:52:16)
	at _PacProxyAgent.addRequest (/usr/share/azuredatastudio/resources/app/node_modules.asar/agent-base/dist/src/index.js:184:38)
	at new ClientRequest (node:_http_client:305:16)

[2023-07-13 22:49:06.329] [exthost] [debug] ProxyResolver#resolveProxy cached https://login.microsoftonline.com/02dca5ee-e24f-4cee-ab0a-1d1054bebd16/oauth2/v2.0/token DIRECT 
Error: Error for stack trace
	at resolveProxy (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:105:69)
	at /usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:294:77
	at new Promise (<anonymous>)
	at _PacProxyAgent.resolveP [as resolver] (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:294:54)
	at _PacProxyAgent.<anonymous> (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:70:37)
	at Generator.next (<anonymous>)
	at /usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:8:71
	at new Promise (<anonymous>)
	at __awaiter (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:4:12)
	at _PacProxyAgent.callback (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/agent.js:52:16)
	at _PacProxyAgent.addRequest (/usr/share/azuredatastudio/resources/app/node_modules.asar/agent-base/dist/src/index.js:184:38)
	at new ClientRequest (node:_http_client:305:16)
	at request (node:https:353:10)
	at Object.patched [as request] (/usr/share/azuredatastudio/resources/app/node_modules.asar/vscode-proxy-agent/out/index.js:298:24)
	at /usr/share/azuredatastudio/resources/app/extensions/azurecore/node_modules/@azure/msal-node/dist/msal-node.cjs.development.js:322:27

Are you missing any proxy settings?

ADS settings reference: https://learn.microsoft.com/en-us/sql/azure-data-studio/azure-connectivity?view=sql-server-ver16#azure-data-studio-proxy-settings
VS Code settings reference: https://code.visualstudio.com/docs/setup/network#_proxy-server-support

bard83 · 2023-07-13T22:38:51Z

I'm not behind any proxy server. I'm tunnelling the connection using ssh through bastion on azure.

bard83 · 2023-07-14T08:39:41Z

Mitigation suggested here helped.

cssuh · 2023-07-14T19:49:52Z

Hi, @bard83 can you please install the latest insiders and run the Azure Accounts: Clear Azure Account Token Cache command? We just pushed out a fix for this issue.

bard83 · 2023-07-15T08:17:07Z

It still does not work.

My test:
The inserders version that you suggested has been installed. The configuration which mitigated the problem has been set back. Azure Account has been cleared. Created Connection and tried con connect.

console-insiders.log

20230715T101037.zip

Anganthier · 2023-07-15T10:22:30Z

Hi,

it works for me.

I removed the current installation of "azure data studio - insider",
deleted ~/.config/azuredatastudio/,
deleted ~/.azuredatastudio-insiders,
installed the azure data studio,
added my ms account
added the connection to the sql server
-> it works, no error showing up

Thanks,
Anganthier

bard83 · 2023-07-17T07:58:26Z

I messed things a little bit up. My bad.

Cleaned up the installations and re-installed the insider version.

It worked. Thanks.

kisantia · 2023-07-18T20:39:21Z

fix has been verified

cheenamalhotra added Bug Area - Azure Triage: Needed labels Jul 7, 2023

cheenamalhotra mentioned this issue Jul 7, 2023

User account not received #23286

Closed

cheenamalhotra added the Needs Logs label Jul 7, 2023

cheenamalhotra added this to the July 2023 Release milestone Jul 7, 2023

cheenamalhotra added Triage: Done and removed Triage: Needed Needs Logs labels Jul 7, 2023

cheenamalhotra closed this as completed Jul 7, 2023

cheenamalhotra reopened this Jul 8, 2023

cheenamalhotra added the Needs More Info label Jul 8, 2023

cheenamalhotra self-assigned this Jul 10, 2023

cheenamalhotra modified the milestones: July 2023 Release, September 2023 Release Jul 12, 2023

cheenamalhotra mentioned this issue Jul 12, 2023

Latest version still have bug: user account not found in MSAL cache please add linked account or refresh account credentials #23351

Closed

cheenamalhotra added the Needs Logs - Azure label Jul 13, 2023

bard83 mentioned this issue Jul 13, 2023

User account not found in MSAL cache on Linux microsoft/vscode-mssql#17744

Closed

cheenamalhotra removed Needs More Info Needs Logs - Azure labels Jul 17, 2023

cheenamalhotra modified the milestones: September 2023 Release, July 2023 Release Jul 17, 2023

cheenamalhotra mentioned this issue Jul 17, 2023

[Release/1.45] Clean encryption keys with cache clear command (#23875) #23903

Merged

kisantia added the Approved label Jul 17, 2023

kisantia closed this as completed Jul 18, 2023

cheenamalhotra mentioned this issue Aug 9, 2023

User account not found in MSAL cache, please add linked account or refresh account credentials. #24104

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

User account not found in MSAL cache on Linux #23688

User account not found in MSAL cache on Linux #23688

cheenamalhotra commented Jul 7, 2023 •

edited

Loading

github-actions bot commented Jul 7, 2023

cheenamalhotra commented Jul 7, 2023 •

edited

Loading

Anganthier commented Jul 8, 2023

Anganthier commented Jul 8, 2023

cheenamalhotra commented Jul 8, 2023

Anganthier commented Jul 9, 2023

cheenamalhotra commented Jul 11, 2023

piyushpaliwal commented Jul 12, 2023

github-actions bot commented Jul 13, 2023

cheenamalhotra commented Jul 13, 2023

bard83 commented Jul 13, 2023 •

edited

Loading

cheenamalhotra commented Jul 13, 2023 •

edited

Loading

bard83 commented Jul 13, 2023

cheenamalhotra commented Jul 13, 2023 •

edited

Loading

bard83 commented Jul 13, 2023

bard83 commented Jul 14, 2023

cssuh commented Jul 14, 2023 •

edited

Loading

bard83 commented Jul 15, 2023

Anganthier commented Jul 15, 2023

bard83 commented Jul 17, 2023

kisantia commented Jul 18, 2023

User account not found in MSAL cache on Linux #23688

User account not found in MSAL cache on Linux #23688

Comments

cheenamalhotra commented Jul 7, 2023 • edited Loading

github-actions bot commented Jul 7, 2023

cheenamalhotra commented Jul 7, 2023 • edited Loading

Anganthier commented Jul 8, 2023

Anganthier commented Jul 8, 2023

cheenamalhotra commented Jul 8, 2023

Anganthier commented Jul 9, 2023

cheenamalhotra commented Jul 11, 2023

piyushpaliwal commented Jul 12, 2023

github-actions bot commented Jul 13, 2023

cheenamalhotra commented Jul 13, 2023

bard83 commented Jul 13, 2023 • edited Loading

cheenamalhotra commented Jul 13, 2023 • edited Loading

bard83 commented Jul 13, 2023

cheenamalhotra commented Jul 13, 2023 • edited Loading

bard83 commented Jul 13, 2023

bard83 commented Jul 14, 2023

cssuh commented Jul 14, 2023 • edited Loading

bard83 commented Jul 15, 2023

Anganthier commented Jul 15, 2023

bard83 commented Jul 17, 2023

kisantia commented Jul 18, 2023

cheenamalhotra commented Jul 7, 2023 •

edited

Loading

cheenamalhotra commented Jul 7, 2023 •

edited

Loading

bard83 commented Jul 13, 2023 •

edited

Loading

cheenamalhotra commented Jul 13, 2023 •

edited

Loading

cheenamalhotra commented Jul 13, 2023 •

edited

Loading

cssuh commented Jul 14, 2023 •

edited

Loading