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

Signed-off-by: Guillaume Tardif <guillaume.tardif@gmail.com>

Signed-off-by: Guillaume Tardif <guillaume.tardif@gmail.com>
This commit is contained in:
Guillaume Tardif 2023-01-13 12:44:08 +01:00 committed by GitHub
parent 47c9478f2a
commit 8a4f8eb776
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 4 deletions

View File

@ -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.