Skip to content
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

Added warning in case of shared key for datalake #2567

Merged
merged 2 commits into from
Feb 6, 2024

Conversation

gapra-msft
Copy link
Member

@gapra-msft gapra-msft commented Feb 5, 2024

Console looks like

INFO: Scanning...
INFO: Autologin not specified.
WARN: *** WARNING *** shared key authentication for datalake is deprecated and will be removed in a future release. Please use shared access signature (SAS) or OAuth for authentication.
INFO: Authenticating to destination using SharedKey
INFO: Any empty folders will be processed, because source and destination both support folders

Log file looks like

2024/02/05 21:18:53 AzcopyVersion 10.23.0
2024/02/05 21:18:53 OS-Environment windows
2024/02/05 21:18:53 OS-Architecture amd64
2024/02/05 21:18:53 Log times are in UTC. Local time is 5 Feb 2024 13:18:53
2024/02/05 21:18:53 ISO 8601 START TIME: to copy files that changed before or after this job started, use the parameter --include-before=2024-02-05T21:18:48Z or --include-after=2024-02-05T21:18:48Z
2024/02/05 21:18:53 WARN: *** WARNING *** shared key authentication for datalake is deprecated and will be removed in a future release. Please use shared access signature (SAS) or OAuth for authentication.
2024/02/05 21:18:53 Authenticating to destination using SharedKey

@vibhansa-msft vibhansa-msft added this to the 10.24 milestone Feb 6, 2024
@gapra-msft gapra-msft merged commit 3b2c00f into main Feb 6, 2024
17 checks passed
@gapra-msft gapra-msft deleted the gapra/sharedKeyDeprecation branch February 6, 2024 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants