-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add More OAuth Providers #2
Comments
Wouldn't Auth0 be a great option since they can then be a proxy for other providers like the ones above? |
I have never really looked into Auth0 all that much. I'll add a reminder to the issue 👍. |
Is there a chance we can get Uber support? |
@maldahleh That sounds like a great idea, but I am relying on other people's contributions for certain services, meaning I have no timeframe as to when that would get added. If you want to contribute, that would be great, if not, no sweat 🙂. |
@calebkleveter I'm implementing Facebook and Twitter logins for my app. I'll get some prototype code working with Github first, to get an idea of how this all fits together, and then I'll take a stab at Facebook and then Twitter. Question: What is the architectural reason for including each provider in the main library? Other similar libraries like OmniAuth have a core library and then you can use the specific provider needed. |
@0xTim - great! I'm trying out the Facebook integration now. I'll let you know if it actually works. :-P |
I pushed up a starter guide for Facebook integration to #19. I have a working implementation in development using SSL. |
Keycloak support is planned? |
@Brouilles I don’t think it is but please send a PR if you do it :) |
For Twitter (now X) see #110 |
GitHub makes a good start for supported OAuth providers, but we need more. Below are a few I would like to add:
or any others that we think would be good.
Note to maintainer: Look into Auth0
The text was updated successfully, but these errors were encountered: