Hello did anyone manage to sign in with a 3rd party e g Twit Supabase #help

Hello, did anyone manage to sign in with a 3rd par...

Timon

01/29/2022, 8:44 PM

Hello, did anyone manage to sign in with a 3rd party (e.g. Twitter) and then use the

provider_token

to make request to the 3rd party API in the name of the authenticated user? When I try to do so, Twitter keeps throwing this error:

Authenticating with OAuth 2.0 Application-Only is forbidden for this endpoint.  Supported authentication types are [OAuth 1.0a User Context, OAuth 2.0 User Context].

Timon

01/30/2022, 2:44 PM

@User is that a known issue of

provider_token

with Twitter API?

jonny

01/31/2022, 8:02 AM

I think it might be because Twitter in Supabase Auth (GoTrue) needs updating to 0Auth2.0

jonny

01/31/2022, 8:04 AM

https://github.com/supabase/supabase/discussions/2270 looks like our twitter docs might be out of date since twitter updated their developer portal

jonny

01/31/2022, 8:05 AM

(for anyone else following this, there's some discussion opened by Timon here https://github.com/supabase/supabase/discussions/2961)

Timon

01/31/2022, 2:54 PM

@User thank you for confirming what I thought. What would you recommend doing? Creating my own sign-in flow sounds like quite a hassle to make it work seamlessly with Supabase client.

jonny

01/31/2022, 2:57 PM

I'll ping the Auth team internally to check out the discussion above

Timon

01/31/2022, 3:12 PM

Great thank you, this is currently a major blocker that may lead many customers to other services than Supabase unfortunately.

Timon

01/31/2022, 3:12 PM

Not being able to query Twitter after the oAuth sign-in makes it practically useless kind of.

xavier

03/04/2022, 8:34 PM

DId you finally make it? I tried with Oauth2 but it seems to be the same

xavier

03/04/2022, 8:36 PM

@User Yes, I'm about to switch to a regular Postgre :/

Previous Next