Why no generic protocol based provider like OIDC, OAuth, ...?

[schewara]

As the list of providers will probably grow, I think it would be good to also have generic providers available to reduce the maintenance overhead and allow friction-less integration of other providers without the need for additional code changes.

Taking some imaginary use cases with OpenID Connect (OIDC) as examples

• using a random certified OIDC Provider (like ORY Hydra, Gluu Server, myID.be, ...)
• upgrading a server with breaking changes (Keycloak 2.x -> Keycloak >= 18.x)

By using generic OIDC with one of the certified OIDC Providers as listed under https://openid.net/developers/certified-openid-connect-implementations/, we can switch providers without having to worry about provider specific features or the need to create a new provider if it is not yet in the list, as long the protocol version is supported.

Python Social Auth for example has such a generic OIDC backend.

Another example would be the Generic OAuth implementation in Grafana, which can be used if you use a different provider.

In a perfect world I would love to see this actually implemented directly in https://github.com/laravel/socialite to reduce the number of project dependencies, but I have no strong opinion about it.

[atymic]

We don't have control over the base Laravel repo, so unfortunately we can't action that.
We would however accept a PR here :)