Update m2m OAuth scopes to not include offline_access.#445
Merged
Conversation
… for m2m, and it's breaking OAuth for AWS.
benc-db
requested review from
andrefurlan-db,
rcypher-databricks and
susodapop
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Including 'offline_access' as a scope in the m2m flow was breaking AWS OAuth. After consulting with Jacky, it seems safe to remove for m2m flow, as it should only be needed for u2m flow.
Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.