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.

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

Document OpenDID SIOPv2 Usage #316

Merged
merged 2 commits into from
Jun 19, 2024
Merged
Changes from 1 commit
Commits
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
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)

OpenDID can be configured to be compatible with [SIOPv2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html).
abdulmth marked this conversation as resolved.
Show resolved Hide resolved
In this case, the authorization can be done only using a DID without the need of any credentials.
abdulmth marked this conversation as resolved.
Show resolved Hide resolved
In order to configure the OpenDID service to allow SIOPv2, it must have a client with an empty requirements
abdulmth marked this conversation as resolved.
Show resolved Hide resolved
value in the `config.yaml` file.

Initiating the SIOPv2 flow is done the same way as the [Implicit Flow](#implicit-flow) with the exception of the `nonce`
abdulmth marked this conversation as resolved.
Show resolved Hide resolved
value being required.
abdulmth marked this conversation as resolved.
Show resolved Hide resolved
Loading