We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
10.20.1
Linux
export AZCOPY_AUTO_LOGIN_TYPE=DEVICE export AZCOPY_TENANT_ID=tenant id ... multiple azcopy commands
Have to enter code into web browser for every azcopy command encountered a script. Not a usable solution when there many commands.
Should be easy to reproduce. It appears from the code that auto-login disables token persistence altogether.
Don't use auto-login, use azcopy login instead, but it's getting removed in 10.22.
azcopy login
Azure CLI persists tokens in ~/.azure folder; could azcopy do the same?
The text was updated successfully, but these errors were encountered:
+1337
Sorry, something went wrong.
This error it's algo present Using azcopy version 10.21.1 under windows 10 19044.3086
Related to this PR #2574
#2747
nakulkar-msft
Successfully merging a pull request may close this issue.
Which version of the AzCopy was used?
10.20.1
Which platform are you using? (ex: Windows, Mac, Linux)
Linux
What command did you run?
export AZCOPY_AUTO_LOGIN_TYPE=DEVICE
export AZCOPY_TENANT_ID=tenant id
... multiple azcopy commands
What problem was encountered?
Have to enter code into web browser for every azcopy command encountered a script. Not a usable solution when there many commands.
How can we reproduce the problem in the simplest way?
Should be easy to reproduce. It appears from the code that auto-login disables token persistence altogether.
Have you found a mitigation/solution?
Don't use auto-login, use
azcopy login
instead, but it's getting removed in 10.22.Azure CLI persists tokens in ~/.azure folder; could azcopy do the same?
The text was updated successfully, but these errors were encountered: