Register login handler?

[jg10-mastodon-social]

This is great!

If I understand correctly, the current approach is to use e.g. a new .auth/github/login route instead of .oidc/auth
I understand the client knows this is supported because it is using the server as an internally generated account.

Would it still be possible to instead or also register a github login handler so this functionality would also be provided to existing apps through the CSS login screen?

https://github.com/CommunitySolidServer/CommunitySolidServer/blob/fa18848281c09fe8685f379891f725ec48a06b10/documentation/markdown/usage/account/login-method.md#updating-the-login-handler

[thhck]

Okay, so you want to know if it's possible to use an SSO (Google, GitHub) as a new login method for CSS?

This is not the goal of my plugin, which aims to take an approach more similar to Supabase authentication—essentially using CSS as a Backend-as-a-Service. I explain more about this here.

However, if you're looking for direct google authentication with CSS, you might be interested in this plugin: css-google-auth (only works with Google).

In my case, I see two different user scenarios: either you're a Solid user, or you're not. If you're not, I think it's cumbersome to create a CSS account using a google login, the get complicated:

solid app --redirect--> CSS auth --redirect--> google auth + consent --callback--> CSS select webId + consent --callback--> solid app

With my plugin, you're asked to log in directly with your SSO, and all the CSS-related details remain hidden. I believe these are two distinct use cases.

That said, I refactored some of my code to align more closely with @ksaito-hiu's source code, so hopefully, it shouldn't be too difficult to support both use cases in the future.