Make CliendID URIs a MUST
This is intended as a conversation starter. If we want to have proper client constraints, for example, acp:client, we need reliable global identifiers for clients. DynReg could be useful during early development, but production systems must always use URIs to denote clients. This way, the redirect_uri gets verified.
related:
- https://github.com/solid/security-considerations/issues/17
I think (hope) we can still make client-side web apps work securely though, if we resume work on https://github.com/solid/webid-oidc-spec/pull/34
By client-side web apps I mean the "client" is the code running in a specific tab in a specific window of a specific browser on a specific device, even if its source code has a global identifier. Similar for smartphone apps.