-
Notifications
You must be signed in to change notification settings - Fork 461
External OAuth Provider Requests #451
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
Comments
Support Steam as an external OAuth ProviderCurrently, Supabase does not support Steam as an external OAuth provider. Describe the solution you'd likeSupport Steam as an external OAuth Provider. https://partner.steamgames.com/doc/features/auth Describe alternatives you've consideredN/A Additional contextThis article describes how Steam's login method works. |
Add Patreon as OAuth providerSupport Patreon oauth. Describe the solution you'd likeSee feature request netlify/gotrue#312 |
Add Quickbooks as an OAuth provider |
Add Orcid as an OAuth providerHi I'd like to publish an app that other researchers can contribute to without signing up to anything, just using the orcid credentials they have for publishing to journals. Could you please add Orcid to the OAuth providers? https://info.orcid.org/documentation/features/public-api/orcid-as-a-sign-in-option-to-your-system/ All the best and many thanks for the great work! |
Add global.id as OAuth ProviderIs your feature request related to a problem? Please describe.Letting users in with a privacy-friendly OAuth Provider while accessing/verifying user data in a privacy-friendly manner if required. Describe the solution you'd likeAdding global.id as sign-in/up option and storing requested data in the user metadata. Describe alternatives you've consideredDidn't really find a good alternative to this provider. Additional contextI would like to implement that but I have never used go before, nor do I have a clue on how to integrate it in the existing codebase. |
Singpass login
Note: Singapore government might move to use SGID |
Foursquare/Swam loginIs your feature request related to a problem? Please describe.Would love to be able to authenticate users with Foursquare/Swarm Describe alternatives you've consideredCurrently using passport-foursquare |
SoundCloud LoginPlease add SoundCloud OAuth provider. Is your feature request related to a problem? Please describe.To extend music streaming platform authentication. Additional contexthttps://developers.soundcloud.com/docs/api/guide#authentication Note: there is an existing PR -- #269 which contains an initial implementation |
Ethereum LoginIs your feature request related to a problem? Please describe.I'd like to let my users log in with their Eth wallet (Metamask, etc) Describe the solution you'd likeJust like Uniswap does. Describe alternatives you've consideredLooks like Redwood has an Eth login. Additional contextn/a Note: there is an existing PR -- #269 which contains an initial implementation |
Auth0Would it be possible to include Auth0 as a login provider. Would like transition over to Supabase however this is preventing me from doing so. Describe alternatives you've consideredTutorial on importing users from Auth0. Relevant resources: |
Tik TokTikTok recently published their OAuth flow Is your feature request related to a problem? Please describe.For the application that I am working on, we convert users from TikTok. Currently, we plan to authenticate them from using Phone authentication, but TikTok support could drastically improve our conversion. Describe the solution you'd likeSocial login with TikTok is supported similar to existing 3rd party providers. Describe alternatives you've consideredThe only other alternative would be to host our own authentication server and use it in tandem with Supabase. Not particularly ideal. Additional contextNote: there is an existing PR -- #269 which contains an initial implementation |
NetlifyAdditional contexthttps://twitter.com/jlengstorf/status/1429611357356187652 https://app.netlify.com/user/applications Relevant Comments:
|
Kakao [ Completed ]Requested on: supabase/supabase#5200 Developer docs: https://developers.kakao.com/product/kakaoLogin Corresponding PR: #366 |
Support GitHub Apps as providerBoth OAuth apps and GitHub Apps use OAuth 2.0. |
I'd love to see Gitlab SELFHOSTED as an option for an auth provider. |
I'm not sure that would serve the purpose of the project. That would only be useful for internal use cases, unless you're going to write it and submit a PR I can't see time being spent on this. Sorry to be blunt. |
Heya, Matt! There's already a Gitlab provider, I'd expect that the only difference between the two is the endpoint. Gitlab encourages self-hosting. While many selfhosted rigs don't use legitimate ssl certs, the vast majority do. If it were truly that simple, I disagree with your assertion that it would serve the purpose of the project. if it were NOT that simple, (I don't know, with confidence, one way or the other, quite honestly.) I can concede the point that time/energy spent likely aren't worth the effort. However, assuming it is that simple, (hey, gotta be optimistic sometimes, right?) I don't see much of a downside... altho admittedly I'm likely missing some significant facet of complication due to ignorance ;) so... can you help me understand what I'm missing? :) |
The main thing I would suggest may prevent this is that the package is focused on Social Auth. ie. Everyone can have a Facebook account, or a Twitter Account, or Google, or x ,y ,z, etc. and if the developer chooses, they can use those services to authenticate. Hope that makes sense. |
Heya Matt! First, thanks for talking about it :) I appreciate the gift of your time and energy. Thank you. I think this might be where our lenses diverge... I'll elucidate my perspective... my intent is not to argue or assert that one or the other is more 'right'.... Rather just trying to express the logic behind my reasoning.. (or what passes for logic between these ears ;) ) As I see it, The package is focused on facilitating external auth for a tool.
Now, a vast majority of users will absolutely lean on ubiquitously-accessible services to provide those tokens, as such, I wholly agree with you that this functionality will only increase the utility derived from the tool for a small cohort of users. However, that doesn't mean that there's no value in the ability to additionally support variant-instantiations of those ubiquitously-available services' facades for less-ubiquitously-available auth-brokers. Nevertheless, Is the use-case for I'd think that's kinda short-sighted, in that The audience diversity of Allowing customers to use their on-prem services to legitimize their users seems like a thing that devs would derive value from, rather than being burdened by.... I was simply figuring that an upside would be a reduction in external network traffic, latencies around auth, as well as greater flexibility offered to app devs to subsequently offer to their customers.. ¯\_(ツ)_/¯ So.. that's the lens I was using when proposing this... |
Yeah, quite burdensome - especially when each installation may differ and having to support different environments complicates things greatly.
The issue I foresee isn't related to cloud or no, it's purely around number of uses that will make use of it.
Completely correct, agreed.
Only in terms of priority, very few users would equate to low priority.
I think there is a slight miscommunication in my message. I am not saying that such an integration would be useless, more than because of the specificity of it's nature and the small cohort that may end up using this, allocating dev time may be a difficult ask. I completely agree there is value in it, but it's substantially less value than a larger, less bespoke integration (bespoke in that there are many more variables for the IdP environment etc. despite being ~ hopefully ~ very similar to the cloud version). I think dev time would be better spent on 'generic' and extensible connectors rather than bespoke solutions for on prem. |
concur on all. Glad to have interacted ;) Thanks for your perspective and input... Totes agree on priority, too. I was mostly just adding the request as if it's not made, there's no way for y'all to gauge interest Thanks for reducing toil for devs. Its appreciated. ❤️🐺w |
## What kind of change does this PR introduce? This PR adds Kakao(https://accounts.kakao.com/) as an external provider. ## What is the current behavior? This provider did not exist before. ## What is the new behavior? Based on Kakao developer docs(https://developers.kakao.com/), this PR creates a provider & test suite for Kakao external provider. ## Additional context Please let me know if there are any changes needed, I do acknowledge that this was once mentioned in another [comment](supabase#451 (comment)), but it seemed like the PR had been frozen since then. I wrote my own version to make sure the tests do pass and the features work properly. --------- Co-authored-by: Kang Ming <[email protected]>
## What kind of change does this PR introduce? This PR adds Kakao(https://accounts.kakao.com/) as an external provider. ## What is the current behavior? This provider did not exist before. ## What is the new behavior? Based on Kakao developer docs(https://developers.kakao.com/), this PR creates a provider & test suite for Kakao external provider. ## Additional context Please let me know if there are any changes needed, I do acknowledge that this was once mentioned in another [comment](supabase#451 (comment)), but it seemed like the PR had been frozen since then. I wrote my own version to make sure the tests do pass and the features work properly. --------- Co-authored-by: Kang Ming <[email protected]>
## What kind of change does this PR introduce? This PR adds Kakao(https://accounts.kakao.com/) as an external provider. ## What is the current behavior? This provider did not exist before. ## What is the new behavior? Based on Kakao developer docs(https://developers.kakao.com/), this PR creates a provider & test suite for Kakao external provider. ## Additional context Please let me know if there are any changes needed, I do acknowledge that this was once mentioned in another [comment](supabase#451 (comment)), but it seemed like the PR had been frozen since then. I wrote my own version to make sure the tests do pass and the features work properly. --------- Co-authored-by: Kang Ming <[email protected]>
Support Google Play Games as providerAlmost every game on Android support Play Games Auth. Seamless(no login screen) authorization is musthave for games. From my point of view flow is very similar for standart auth via google. Some privious requests: |
Support AT Protocol (incl. Bluesky) as a providerThis will allow to build applications on top of AT Protocol easily. https://docs.bsky.app/blog/oauth-atproto |
AGREE! |
Support Authentik as an external OAuth ProviderDescribe the solution you'd likeSupport Authentik as an external OAuth Provider. Describe alternatives you've consideredN/A Additional contextThis article describes Authentik OAuth2 providers. |
QQ as OAuth providerQQ is the second most widely used social platform in China (the most one is WeChat). It has ~600 million monthly active users. Documents are here, thanks ❤️ |
Support Naver as ProviderAccording to recent information, Naver has approximately 40 million active users in South Korea, making it the dominant search engine in the country. Having Kakao as auth provider is great but naver is more than necesary. |
I also think so |
Support Tiktok as an external OAuth ProviderCurrently, Supabase does not support Titktok as an external OAuth provider. Describe the solution you'd likeSupport Tiktok as an external OAuth Provider. https://developers.tiktok.com/doc/login-kit-desktop Describe alternatives you've consideredN/A Additional contextThis article describes how Tiktok's login method works. This PR did implement Tiktok as a provider but was never merged because it was supposed to be opened as an individual PR for better readability and testing |
Support Reddit as an external OAuth ProviderDescribe the solution you'd likeSupport Reddit as an external OAuth Provider. Describe alternatives you've consideredN/A Additional contextThis article provides an overview of Reddit's OAuth2 providers. While the resource appears outdated, it remains functional. |
Support ARES as an external OAuth ProviderDescribe the solution you'd likeSupport ARES as an external OAuth Provider. This is necessary for partners to integrate ARES as a sign in option and the access token is required to call the IdP's APIs. Describe alternatives you've consideredUsing a third-party auth like Auth0 but that messes with the existing supabase auth and there's barely any documentation from Supabase about integrating Auth0. It doesn't work. Additional contexthttps://pantheon-technologies.gitbook.io/ares-for-partners |
Support Tiktok as an external OAuth Provider Describe the solution you'd like Describe alternatives you've considered Additional context #269 did implement Tiktok as a provider but was never merged because it was supposed to be opened as an individual PR for better readability and testing |
Vipps OAuth ProviderAdd support for Vipps, the no. 1 mobile payment provider in Norway - https://developer.vippsmobilepay.com/docs/APIs/login-api/ Additional context |
How about for Instagram? |
Is there any update or rough timeline for this? This issue has been open for a while, and having even a rough idea of the support timeline would be really helpful for Supabase users to plan their own product roadmaps accordingly. |
@thealishakeri I create PR again for TikTok, but no reviews from the team. |
how about Snapchat as an authentication method ? |
Uh oh!
There was an error while loading. Please reload this page.
This issue is for tracking requests/demand for integration with External OAuth Providers. Give a comment a thumbs up if you want the connector built or drop a comment if you wish to work on any of the providers below.
We will prioritise providers based on the number of upvotes/thumbs up so do upvote your favourite providers
The text was updated successfully, but these errors were encountered: