Removed remaining ref to backend service in oauth flow doc (#16515)

Signed-off-by: Guillaume Tardif <[email protected]> Signed-off-by: Guillaume Tardif <[email protected]>
docker · Jan 13, 2023 · 8a4f8eb · 8a4f8eb
1 parent 47c9478
commit 8a4f8eb
Showing 1 changed file with 0 additions and 4 deletions.
diff --git a/desktop/extensions-sdk/guides/oauth2-flow.md b/desktop/extensions-sdk/guides/oauth2-flow.md
@@ -80,10 +80,6 @@ POST https://authorization-server.com/token
 >
 > The client's credentials are included in the `POST` query params in this example. OAuth authorization servers may require that the credentials are sent as a HTTP Basic Authentication header or might support different formats. See your OAuth provider docs for details.
 
-#### Token Endpoint Response
-
-Finally, you can read the access token from the HTTP response and pass it to the extension UI by having the browser after OAuth be redirected to the backend service. The backend service, in turn, has to explicitly redirect the browser to `docker-desktop://dashboard/open`.
-
 ## Step three: Store the access token
 
 The Docker Extensions SDK doesn't currently provide a specific mechanism to store secrets.