-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add-AzureAccount does not create TokenCache.dat #4080
Comments
some more information. debug shows the call Microsoft.Azure.Commands.Common.Authentication.ProtectedFileTokenCache.AfterAccessNotification was not called during the token creation. Even for this one Microsoft.Azure.Commands.Common.Authentication.ProtectedFileTokenCache..ctor(Byte[]) |
@afengli would you mind providing us with the debug output when executing this cmdlet? You can do so by setting Also do you have permissions to read/write in "AppData/Roaming/Windows Azure PowerShell"? |
@cormacpayne , yes I am doing it. you can also try to reproduce it easily. I see multiple instances that the 4.x version module broke the authentication and Azure context. |
@cormacpayne |
Fixed. Will ship in in July release |
Cmdlet(s)
PowerShell Version
Instructions: to get PowerShell version, type
$PSVersionTable
and look for the value associated withPSVersion
5.1.14393.1198
Module Version
4.0.2
OS Version
Instructions: to get OS version, type
$PSversionTable
and look for value associated withBuildVersion
10.0.14393.1198
Description
Add-AzureAccount does not create TokenCache.dat. This will cause command like Get-AzureService to fail.
Debug Output
Instructions: to get Debug Output, set
$DebugPreference="Continue"
and then execute the cmdlet or script causing the issueScript/Steps for Reproduction
Try this script:
The text was updated successfully, but these errors were encountered: