-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
doc_update_oath_issue_gsc #17967
Merged
Merged
doc_update_oath_issue_gsc #17967
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change depreciated > deprecated
Delete "Thank you for your patience!"
Do we have a timeline for the fix? Also, do we have a workaround/alternative for now?
Are other connectors affected by this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No timeline and as far as we know, this only impacts GSC.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, if we don't have a timeline for the fix, we shouldn't mention it in docs. How about "Google has deprecated certain OAuth workflows. Before you use this connector, verify that the deprecated workflows don't impact your setup."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are working on a fix (GL backlog) but we don't have an official timeline as we don't fully understand the scope yet. Note that the OAuth deprecation affects our connector (in other word, customers are impacted as a result of an issue on our side, not their side) so I don't think we can ask them to check their workflows. Do you have some other suggestions on how we can best convey this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha. In that case, I think we need to give users actionable guidance and ask them to use the alternative method (Service Account, I think?)
How about "Since Google has deprecated certain OAuth workflows, OAuth isn't supported for this connector." And then remove all OAuth-related content from the doc for now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Amruta! I think that's fair for now. Can we say "Since Google has deprecated certain OAuth workflows, OAuth isn't supported for this connector at this time.". We are working on a fix so we don't want to give the impression that this is permanent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, sounds good!