The PassportJS security module of Wiki is the main authentication client in the federation, next to friends. While it supports generic OAuth2 endpoints, these are often hard to configure and generally tend to fall apart.
Meanwhile the OpenID Connect (OIDC) ecosystem has further stabilised on top of OAuth2, originally an authorization protocol, and provides nice convenience features for set up.
Supporting OIDC would bring support for the .well-known/openid-configuration endpoint, where supported, and reduces setting up an OIDC identity provider to providing three values: the client ID, the client secret and said well-known OpenID configuration URL.
This makes it very easy and convenient to set up client connections.
With increasing adoption of self-hosted authentication providers, adoption of OpenID could also help more people to provide their farm with self-rolled identity.
The PassportJS security module of Wiki is the main authentication client in the federation, next to friends. While it supports generic OAuth2 endpoints, these are often hard to configure and generally tend to fall apart.
Meanwhile the OpenID Connect (OIDC) ecosystem has further stabilised on top of OAuth2, originally an authorization protocol, and provides nice convenience features for set up.
Supporting OIDC would bring support for the
.well-known/openid-configurationendpoint, where supported, and reduces setting up an OIDC identity provider to providing three values: the client ID, the client secret and said well-known OpenID configuration URL.This makes it very easy and convenient to set up client connections.
With increasing adoption of self-hosted authentication providers, adoption of OpenID could also help more people to provide their farm with self-rolled identity.