-
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
Fix TokenCache initialization when importing a context #7456
Comments
Hi, I am experiencing this issue and the workaround at #7110 is not helping me.. why solve such a critical issue on december?? all our scripts fail now!! |
This issue need to be reopen. There's no indication it has been fix, nor which version will contain the fix. The issue still exist with Az Module 0.5.0. For now, the only workaround is to use the Enable-AzContextAutoSave cmdlet.
|
@MaximoTrinidad This is the issue that tracks a fix for this - the referenced issue was closed as a duplkicate, to make tracking the fix easier. Meanwhile, if you are using PowerShell interactively, consider using context autosave instead of importing and exporting contexts. Context autosave automatically saves your available contexts in between sessions, making it unnecessary to improt and export contextts. If you are mainly running scripts in PowerShell, here is some advice: (1) Turn off context autosave, as this will make all authentication occur in memory, and isolate each session from the context changes in other sessions ( |
Hi @markcowl!! Thanks for the advice! |
Candidate fix for this issue is here: #7949 |
Fix is checked in. will be in 12/18 release. |
That's Awesome!! Looking forward to it. |
I know there's an urgency in closing resolving open issues, but I would recommend to re-open this issue as it hasn't been release yet and tested by users. For example, issues closed #7954 and #7956 on module version 0.6.1 shows closed but remains broken in module version 0.7.0. This issue is causing people to go back and install the old AzureRM modules so their scripts won't break. Is just my opinion! :) |
@MaximoTrinidad totally agree, cannot rely on these modules anymore, every update is just scary, you have no idea when and where you will need to work hours to understand what MS has broken -_- |
Although, this has been close for awhile... I just want to say... This is finally working on Az Module Version 1.0 released on December 18th. Woohoo!! |
@MaximoTrinidad this is not fully resolved. |
If you feel it isn't working. I suggest to open a new incident so it can be track down. This will create visibility. The issues I was having seems all gone. :) |
@MaximoTrinidad Not enough time in the day to open an issue on this 😆 |
Description
When importing a saved context container with multiple contexts, the existing token cache should be overwritten with the token cache for the default context.
Instead, the token cache is cleared and the user must log in again.
Cost: 6
The text was updated successfully, but these errors were encountered: