Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document OpenDID SIOPv2 Usage #316

Merged
merged 2 commits into from
Jun 19, 2024
Merged

Document OpenDID SIOPv2 Usage #316

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1ab3bf6
SIOPv2
abdulmth Jun 17, 2024
e1089f1
Apply suggestions from code review
abdulmth Jun 18, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/develop/08_opendid/04_integrate_opendid.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,3 +114,13 @@ After successful authentication, OpenDID redirects back to the provided `redirec
state=nitctpl7nmqcpvob7xthrw&
token_type=bearer
```

## Self-Issued OpenID Provider v2 (SIOPv2)

You can configure OpenDID to be compatible with [SIOPv2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html).
In this case, you only need a DID for the authorization, and no credentials.
To configure the OpenDID service to allow SIOPv2, it must have a `client` key with an empty requirements
value in the `config.yaml` file.

Initiate the SIOPv2 flow the same way as the [Implicit Flow](#implicit-flow) with the exception that the `nonce`
value is required.
Loading