Workaround for the token cache issue in Az.Accounts 2.1.0#13362
Workaround for the token cache issue in Az.Accounts 2.1.0#13362
Conversation
Using version 1.9.5 of Az.Accounts.
|
Thank you for your contribution dineshreddy007! We will review the pull request and get back to you soon. |
|
/azp run azure-powershell - powershell-core |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run azure-powershell - security-tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Will send a new iteration with a different workaround as per Yeming's suggestion. |
Using AuthFactory.Authenticate instead of TokenCache
|
/azp run azure-powershell - security-tools |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run azure-powershell - windows-powershell |
|
Azure Pipelines successfully started running 1 pipeline(s). |
They'll be updated automatically during release process
isra-fel
left a comment
There was a problem hiding this comment.
Hi @dineshreddy007 versions are calculated automatically during release process, so I've reverted psd1 and AssemblyInfo.cs.
Have you tested the new work-around? Is it ready for a release?
|
Hi @isra-fel i have tested the workaround and it is ready for release. |
I have tested the workaround and it is ready for release. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Description
TokenCache.ReadItems() is not working in latest version 2.1.0 of Az.Accounts. As a workaround using AuthFactory.Authenticate() instead of TokenCache.ReadItems().
Checklist
CONTRIBUTING.mdChangeLog.mdfile(s) has been updated:ChangeLog.mdfile can be found atsrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md## Upcoming Releaseheader -- no new version header should be added