Update Google Analytics Oauth flow #6321
Merged
Conversation
This file contains 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
sherifnada
approved these changes
Sep 20, 2021
| @Override | ||
| protected Map<String, Object> extractRefreshToken(JsonNode data) throws IOException { | ||
| // the config object containing refresh token is nested inside the "auth_mechanism" object | ||
| return Map.of("auth_mechanism", super.extractRefreshToken(data)); |
There was a problem hiding this comment.
can we use the name credentials instead of auth_mechanism to standardize this across connectors? I'll see to it that the downstream PR is updated
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Update Google Analytics OAuth flow implementation to be compatible with connector's change in #6306
How
OAuth params are moved and nested into
auth_mechanism