Remove GitHub Auth related stuff?

[kentcdodds]

I'm considering removing GitHub auth related stuff (I actually am going to be adding PassKey support soon). This would involve a database migration to remove the connections and it would remove all the connections UI from the account management page. I'm just not sure how many people using the Epic stack actually benefit from having all of that code even if you don't end up using GitHub auth. If you wind up adding different OAuth providers, having the GitHub auth in there by default can be really useful. But I think we just move that to an example and people add that manually themselves. I'm just curious what people are doing with the GitHub auth when they start new projects.

So, are you using GitHub auth?

[rajeshg]

I use google auth much more often, so I switch up the github auth implementation with google auth when I start new projects. Having some external provider by default, is helpful for me.

[cr101]

I agree that it’s very helpful to have an external provider by default. I switch the GitHub auth implementation with LinkedIn auth for new projects.

[jpricer]

Same, for initial dev work having it there as a model is great since most all devs have an account and so from the start can easily trace the complete auth flow to figure things out. My clients mainly use other auth providers but having this one in place makes it easier to see how to add those (although I suppose examples would work as well). Also I feel if it was wasn't there I would be less inclined to add my own and instead reach for other third party auth services like firebase, fusionauth, etc. Those often come with RBAC, tenant and other features which are fine but duplicate and confuse where/how to manage users, I like the simplicity of having it integrated.

[kentcdodds]

I’ve talked with others offline who said similar things! I’ll keep it built in. Thank you all for your feedback!

[jpricer]

Good the hear. Also +1 for PassKey support, would love to see how it is done!

[DennisKraaijeveld]

All my projects are for regular clients thus Github auth is the first thing I remove and add Google instead. Github Auth in my opinion is only useful when your application is developed for other developers.. which I think is only a small percentage of all projects created with Epic Stack? It would be beneficial to replace GH auth with something more universal like Google and let that be an example to let users add Linkedin, Facebook, Github etc etc.

[sergiodxa]

The benefit of GH is that, for the dev using EpicStack, it's way simpler to get a client id and client secret IMO, and the process to use GH and Google is similar (both are OAuth2 based).

[kentcdodds]

This is exactly the reason that I used Github instead of Google when I added this authentication feature as a built-in feature of the Epic Stack. And I made sure to make it very easy to swap out providers, because I figured most people wouldn't actually want the Github auth provider but it's definitely the easiest one to set up for developers.

I am considering playing around with OpenAuth as an alternative to the built-in authentication strategy and potentially swapping it out entirely, as long as I can keep things very simple with deployment, which I think is possible.

[sergiodxa]

It should be possible to run OpenAuth inside a splat route.