From 8a4f8eb776fa49233eca283556b47a13d15d1d72 Mon Sep 17 00:00:00 2001 From: Guillaume Tardif Date: Fri, 13 Jan 2023 12:44:08 +0100 Subject: [PATCH] Removed remaining ref to backend service in oauth flow doc (#16515) Signed-off-by: Guillaume Tardif Signed-off-by: Guillaume Tardif --- desktop/extensions-sdk/guides/oauth2-flow.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/desktop/extensions-sdk/guides/oauth2-flow.md b/desktop/extensions-sdk/guides/oauth2-flow.md index c1ded2b3d3..8edb39daa8 100644 --- 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.