From 1b297b74ced1e6460e16f0c241b1d92d1ab7531e Mon Sep 17 00:00:00 2001 From: Abdulrahim Al Methiab <31316147+abdulmth@users.noreply.github.com> Date: Wed, 19 Jun 2024 16:43:59 +0200 Subject: [PATCH] Document OpenDID SIOPv2 Usage (#316) * SIOPv2 * Apply suggestions from code review Co-authored-by: Chris Chinchilla --------- Co-authored-by: Chris Chinchilla --- docs/develop/08_opendid/04_integrate_opendid.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/develop/08_opendid/04_integrate_opendid.md b/docs/develop/08_opendid/04_integrate_opendid.md index 6757cee95..36836654a 100644 --- a/docs/develop/08_opendid/04_integrate_opendid.md +++ b/docs/develop/08_opendid/04_integrate_opendid.md @@ -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.