Re: Usability and scalability of Solid-OIDC in a decentralized ecosystem

Hi Virginia,

I see Client ID which dereferencse to Client ID Document as the correct 
approach.

https://solid.github.io/solid-oidc/#clientids

I believe Solid-OIDC providers are not required to support Dynamic 
client registration so trying to rely on it seems like poor assumption 
from the start.
Besides that dynamic identifiers are practically useless when setting a 
client restrictions using for example `acp:client` matchers.

Do you seen the issues you mention still applicable when Client IDs 
which dereference to Client ID Documents are used?

Cheers,
elf Pavlik

On 2025-04-22 09:30, Virginia Balseiro wrote:
> Hi all, I want to ask a potentially silly question about Solid-OIDC :)
> 
> AFAICT, with static registration, clients need to be very aware of 
> IDPs,
> registering themselves statically (read: manually) on a particular
> "broker" service. This means it is not particularly scalable for a
> decentralized ecosystem.
> 
> Dynamic client registration is perhaps more suitable for a 
> decentralized
> ecosystem, but the benefits in terms of security seem marginal since 
> any
> client can register themselves dynamically. 
> 
> In addition, there have been conversations (and there might have been
> implementations) about potential restrictions of certain operations
> and/or certain resources to particular clients means that users will
> need to contact / request their RP / service providers to allow a
> certain application that they prefer / trust.
> 
> These approaches sound for sure very secure, but doesn't seem to align
> to the promise of individuals having the "autonomy" that Solid is
> supposed to offer.
> 
> I may have misunderstood some of the technical details but it seems to
> me (Solid-)OIDC's model isn't particularly fitting for Solid. My
> question is, how would this be reasonably usable and scalable in a
> decentralized / open ecosystem?
> 
> Cheers,
> 
> Virginia
> https://virginiabalseiro.com/#me

Received on Tuesday, 22 April 2025 16:20:03 UTC