Skip to content

Commit

Permalink
Fixes
Browse files Browse the repository at this point in the history
Signed-off-by: Chris Chinchilla <[email protected]>
  • Loading branch information
ChrisChinchilla committed Jun 11, 2024
1 parent 04a3ba7 commit 1563bcf
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 5 deletions.
4 changes: 2 additions & 2 deletions docs/develop/08_opendid/02_opendid_flow.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Common use cases include the following:
- OpenDID back end
- Identity wallet that follows [the Credential API spec](https://github.com/KILTprotocol/spec-ext-credential-api) (typically a browser extension, for example, [Sporran](https://www.sporran.org/))

The following steps outline the interactions necessary to implement the Implicit Flow:
The following steps outline the interactions necessary to implement [the implicit flow](https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth):

1. The user clicks the login button on the *web app front end*.
2. The *web app front end* redirects the user to the *OpenDID front end*.
Expand Down Expand Up @@ -69,6 +69,6 @@ AB->>AF: (10) Access granted.
```

:::info
Although this example describes the implicit flow, the authorization code flow is similar.
Although this example describes the implicit flow, [the authorization code flow](https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) is similar.
Instead of returning an `id_token` directly, the OpenDID service instead returns a `code` to exchange for an `id_token` using the `token` endpoint.
:::
5 changes: 2 additions & 3 deletions docs/develop/08_opendid/04_integrate_opendid.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,11 @@ Read the [demo project guide](05_demo_project.md) for an example of integrating

## Authorization code flow

Initiate the flow by redirecting to the **GET** `/api/v1/authorize` endpoint on the OpenDID service and setting the following query
parameters:
Initiate the flow by redirecting to the **GET** `/api/v1/authorize` endpoint on the OpenDID service and setting the following query URL-encoded parameters:

- `response_type`: set value to `code` to indicate Authorization Code Flow.
- `client_id`: The client ID set in the `config.yaml` file.
- `redirect_uri`: OpenDID will redirect to this URL after authentication.
- `redirect_uri`: OpenDID redirects to this URL after authentication.
- `scope`: set value to `openid`.
- `state`: set to a secure random number.
- `nonce`: optional value, set to a secure random number.
Expand Down

0 comments on commit 1563bcf

Please sign in to comment.