Diego81 / omnicontacts

A generalized Rack middleware for importing contacts from major email providers.
477 stars 230 forks source link

Yahoo OAuth 2 #169

Closed Alagaesia93 closed 6 years ago

Alagaesia93 commented 7 years ago

Hi guys, I'm currently integrating your gem in my app and Yahoo does not work. It looks like that Yahoo has updated from OAuth 1 to OAuth 2 (yeah, very fast!). Further explanation here https://www.sourcecoast.com/forums/jfbconnect/jfbconnect-joomla-3x-support/12438-yahoo-api-error#p61158

Thank you very much and congrats for your gem, it's great!

katiemccann commented 7 years ago

Yahoo is still working fine in my app, could you provide a little more detail on the error you're getting?

teodor2903 commented 7 years ago

Hi, I have same trouble This is from log: Started GET "/contacts/yahoo/callback?oauth_token=bv9zukb&oauth_verifier=5vdhy8" for 178.165.91.196 at 2017-04-18 05:56:52 +0000 I, [2017-04-18T05:56:54.593690 #16559] INFO -- : [c155d79d-6875-4d28-986f-15131efb6736] Started GET "/contacts/failure?error_message=internal_error&importer=yahoo" for 178.165.91.196 at 2017-04-18 05:56:54 +0000 I, [2017-04-18T05:56:54.596196 #16559] INFO -- : [c155d79d-6875-4d28-986f-15131efb6736] Processing by Api::NewsletterRecipientsController#contacts_failure as HTML I, [2017-04-18T05:56:54.596300 #16559] INFO -- : [c155d79d-6875-4d28-986f-15131efb6736] Parameters: {"error_message"=>"internal_error", "importer"=>"yahoo"}

jr180180 commented 7 years ago

Tested this with Yahoo today and the integration still works well. I wonder if that internal_error was just a temporary thing?

ghost commented 6 years ago

I'm encountering this same error, here's the log I got from the gem: Error internal_error while processing /contacts/yahoo/callback: {"error":{"@lang":"en-US","@uri":"http://yahoo.com","description":"Access forbidden for the user as cookie validation failed","detail":"Access forbidden for the user as cookie validation failed"}}

katiemccann commented 6 years ago

The cookie validation failure is under a separate issue, since there are no more reports of the original issue, closing this.