> Il 26/02/2021 17:32 Aaron Parecki <aa...@parecki.com> ha scritto: > > > Dynamic client registration does exist in OAuth: > https://tools.ietf.org/html/rfc7591 > > The point is that basically nobody uses it because they don't want to > allow arbitrary client registration at their ASs. That's likely due to a > combination of pre-registration being the default model in OAuth for so long > (the Dynamic Client Registration draft was published several years after > OAuth 2.0), as well as how large corporations have decided to run their ASs > where they want to have (what feels like) more control over the things > talking to their servers. > This is indeed a matter of product design. I am active in an OIDC-based open identity project where the specs say that providers MUST accept dynamic client registration, without a pre-determined client secret. This is the only way to create a federation that can work on an Internet scale, with relying parties accepting identities managed by providers unknown to them. Then, of course, this also creates lots of opportunities for abuse: you end up in an email-like scenario in which you need ways to ascertain trust in unknown parties and decide whether you want to accept interoperating with them and believe the information they provide, which in turn depends a lot on your specific use case. But we think that that is preferrable to the centralization that is inherent in the original registration model.
-- Vittorio Bertola | Head of Policy & Innovation, Open-Xchange vittorio.bert...@open-xchange.com mailto:vittorio.bert...@open-xchange.com Office @ Via Treviso 12, 10144 Torino, Italy
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
