@JadedBlueEyes @Arusekk
i don't think open source is broken, i only intend to put more thought into what i contribute, why, and its effects.
while i'm not going to write an OIDC library, i would still be up for working on decentralised auth, but i would insist on revisiting the assumptions baked into the protocol, for example:
- is a third-party identity provider strictly necessary? we do have examples of identity attestation without one, i.e. ssh
- the core/standard claims can go, especially the gender one, with prejudice
if the identity provider is necessary for a given use case:
- does the identity provider need to be aware of which service the user is authenticating with?
- can we build more redundancy and/or migration between identity providers into the protocol, so that any given provider becomes less central and powerful?
- why is it necessary? i think many services use it as an assurance that a user is a real individual, and not part of a bot swarm. not all providers serve this need equally, and their answers for it typically lie outside the protocol. this favours big providers, and i think it's part of why they see OIDC as furthering their ends, not threatening them. is there something we could do in the protocol to counteract that?
big providers benefit from these assumptions being baked into the standard and taken as given. by revisiting these, i think i could make something that has the positive effects i want while avoiding the negative externalities.
the only reason i haven't started on this is that i think good implementations need to be use driven, and i don't currently have a use case. the work project is a non starter since there OIDC is not a technical choice, it's mandated by the provider, that's in turn mandated by management.