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

Fixed a bug where preserve permissions would not work with OAuth #1963

Merged
merged 2 commits into from
Nov 21, 2022

Conversation

gapra-msft
Copy link
Member

No description provided.

jpm.secondarySourceProviderPipeline = NewBlobFSPipeline(
azbfs.NewAnonymousCredential(),
credential,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this something that hits only in creating secondarySource. As function is createPipeline sounds like having a wrong credential here should have never worked so just want to understand what condition is failing here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this works when using SAS since anonymous credential is for SAS. But if customer uses OAuth we never set that credential (it was anonymous cred)_so we failed for all datalake endpoint operations w/ OAuth

Copy link
Contributor

@siminsavani-msft siminsavani-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@gapra-msft gapra-msft merged commit e6c1b7a into dev Nov 21, 2022
@gapra-msft gapra-msft deleted the gapra/getACLOAuth branch November 21, 2022 17:21
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.

3 participants