Skip to content

Support for Client ID Documents #104

Open

Description

@michielbdejong

As per https://github.com/solid/solid-oidc/blob/a5a966c7342da01a57bfb316e5533ea7d82fd245/index.bs#L163-L166

The serialized JSON form of a Client ID Document SHOULD use the normative JSON-LD @context
provided at https://www.w3.org/ns/solid/oidc-context.jsonld such that the resulting
document produces a JSON serialization of an OIDC client registration, per the
definition of client registration metadata from [!RFC7591] section 2.

Activity

  1. michielbdejong commented on Oct 6, 2022

    @michielbdejong
    MemberAuthor

    This also implies that clientId is an IRI which means it doesn't easily fit into routes like

    ['name' => 'page#approval', 'url' => '/sharing/{clientId}', 'verb' => 'GET'],
    ['name' => 'page#handleRevoke', 'url' => '/revoke/{clientId}', 'verb' => 'GET'],
    ['name' => 'page#handleApproval', 'url' => '/sharing/{clientId}', 'verb' => 'POST'],

  2. added this to the v0.8.0 milestone on Oct 19, 2022
  3. removed this from the v0.8.0 milestone on Jan 20, 2024
  4. added this to the v0.10.0 milestone on Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions