Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Update CWS web API docs to reflect updated OAuth token guidance #3699

Open
dotproto opened this issue Sep 13, 2022 · 1 comment
Open

Update CWS web API docs to reflect updated OAuth token guidance #3699

dotproto opened this issue Sep 13, 2022 · 1 comment
Assignees
Labels
Chrome-Web-Store content update extensions Issues related to extensions documentation. P1 A high priority task. This task *must* be completed soon. transferred

Comments

@dotproto
Copy link
Contributor

dotproto commented Sep 13, 2022

The Using the Chrome Web Store Publish API documentation currently advises extensions developers to acquire an OAuth token using Google OAuth's out of bad (OOB) flow. This flow is being deprecated (blog post).

OAuth out-of-band (oob) flow will be deprecated (link)

OAuth out-of-band (OOB) is a legacy flow developed to support native clients which do not have a redirect URI like web apps to accept the credentials after a user approves an OAuth consent request. The OOB flow poses a remote phishing risk and clients must migrate to an alternative method to protect against this vulnerability. New clients will be unable to use this flow starting on Feb 28, 2022.

We need to update our documentation to reflect the new recommended flow: Loopback IP address flow.

Related issues

@dotproto dotproto added P1 A high priority task. This task *must* be completed soon. extensions Issues related to extensions documentation. content update labels Sep 13, 2022
@dotproto
Copy link
Contributor Author

The current recommendation is that developers use the Loopback IP address flow.

To address potential confusion (I was confused), the blog post indicates that the "Loopback IP address flow" is being disallowed in some cases. At first I thought this applied to us as well, but it seems that desktop applications are still allowed to use this flow and it appears that our use case qualifies.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Chrome-Web-Store content update extensions Issues related to extensions documentation. P1 A high priority task. This task *must* be completed soon. transferred
Projects
None yet
Development

No branches or pull requests

3 participants