Closed osmant closed 6 years ago
Hi osmant, Thanks a lot for your analysis!
You are right, this is an issue caused by the changes of Azure Account extension which we depends on. The week before last week Azure Account upgraded to 0.3.0, in which version the credential _entries was moved into target property, which breaks our authentication module.
We released a new version(0.2.9) last week and fixed the issue, could you please try the new one? We highly appreciate your detailed analysis on this issue.
Thanks, Tiger
Hi @tigerenwork,
Thanks for the update. I have just upgraded the extension to v 0.2.9 and it started to work.
Regards
Hi,
I am having problems when trying to connect Azure Data Lake and see my ADL accounts. Let me explain what I do and what happens after all.
This command is returning me following message
Then nothing is listed. Normally I would expect Azure Data Analytics account to be listed there. Not only this command was failing, Data Lake Explorer was showing my subscription fine but when I want to see the ADLA account, it was not working. Also I can not submit/compile any usql file.
At this point what I did is, as mostly suggested, I looked at the Developer tools. In developer tools I found a error message as following.
As indicated in the error message, I found the authenticationManager.js file in the path which error message is referring to and following method in the file.
It was not super easy to debug this method, but with a lot of console.log(object), I got to know that following lines is the one causing an exception.
in the first method
tokens
is being assigned tonull
and thereforefind
function throws an error.The reason why
tokens
is beingnull
is becausesession.credentials["tokenCache"]
object does not have property_entries
When I log the
session.credentials["tokenCache"]
to console, I noticed that expected_entries
array is not there. In fact,_entries
array is beneathtarget
property. Please check following screenshot.Hence the code was throwing an exception. I don't know whether this is general bug or not. But once I changed all
session.credentials["tokenCache"]._entries;
intosession.credentials["tokenCache"].target._entries;
Everything started to work as expected. It was tedious problem because suddenly my development environment stopped working. I just wanted to share in case if it requires any action from on developer of this add-in.
Regards