I just implement Omniauth+Devise to signin using Google Apps, but when doing the request and the "Request phase initiated" my app get blocked, i tried a request in another window and it didnt execute untill the "Request Phase" was over, several secods later.
im using omniauth-openid, omniauth-google-apps and Devise gems.
Related
I tried the soundcloud developer portal and got a google prompt to not available to sign up a new app. the message read the following. SoundCloud Application Registration Due to the high amount of requests recently received, we will no longer be processing API application requests at this time. We are working to re-evaluate our process to make it more efficient.
After following this link on how to setup omniauth using google in a rails app, I noticed that the call back url was different from what I supplied in the google api console.
My question however is that, why is the call back url that I provided in the google API console different from the call back that google is redirecting to my app
FYI - I have the gem 'omniauth-google-oauth2' in my Gemfile
I am having trouble with facebook API call. I am using Koala for server side api call but recently came into issue making api call. So I tried to bypass koala call and did raw api http call using call but to no avail.
When I do curl from development machine it works fine.
curl "https://graph.facebook.com/me?oauth_token=my_token
It returns profile details, but the same thing done from production machine, it's throwing the exception
{"error":{"message":"Cannot call API on behalf of this user","type":"OAuthException","code":200}}
Does anyone had the same issue? Like to hear from you guys.
I found the source of the problem (on our site, at least). In Facebook's developer console (https://developers.facebook.com/apps), our app was showing an invalid privacy policy. Due to this, Facebook had automatically placed our app into Sandbox Mode.
Updating our privacy policy and (more notably) removing our app from Sandbox Mode caused this error to cease.
Other users seem to have had some success with removing regional (country-specific) restrictions on who can and cannot log in to their app (https://groups.google.com/forum/#!topic/django-social-auth/XaE5dFXEqhA)
Best of luck! :)
I had the App in dev mode. All I did was remove the subscription & resubscribe my webhook server and this worked for me.
Hi all: I'm trying to test a hangout app, running from the API Console link/in the Sandbox.
Machines are
- Mac OS X,
- latest normal Chrome.
Both users are
- Google Apps users,
- added to API Team for hangout project,
- able to see the App Engine application for static files etc.
User one is API project owner, user two can view project.
As user one, I click the API Console/Sandbox link to start.
The plugin starts, and the app starts right away.
I click on the App icon at left to hide the app.
I click on the blue Invite People button to invite user two.
The app frame goes blank, no way to invite user two.
In user one's console, there's only one error, prior to app startup:
Failed to load resource: the server responded with a status of 404 (Not Found)
https://hangoutsapi.talkgadget.google.com/talkgadget/channel
Starting with user two, I get two errors--first the following, followed by the above error, followed by app startup:
Uncaught TypeError: Cannot call method 'isLoaded' of undefined
:87
The stacktrace of this error goes
0d.be :87
init: (program):1
onload :1
0d.load :1
Gg :120
window.jstiming.js :124
(anonymous function) :371
... no file names, just line numbers.
I have not gone through the OAuth client ID configuration yet. Is this needed for Sandbox work between two users (as opposed to individually)?
I need a way to get these two users into the same hangout. Eventually I can do this through server-sent URLs (I believe) but for yesterday I need a quick 'n' dirty method.
Many thanks for any insight.
Kirk.
Instead of trying to use Invite, you may want to send the URL of the sandboxed hangout to the other person.
You may also want to skip the sandbox altogether and just publish the code and work with the "public" version.
I have a Rails app that sends requests to a Node.js app. The node.js app processes the requests and returns to the Rails app.
This is all done synchronously in the Rails app (the app blocks until Node.js returns). However, what I intend to do is make this non-blocking.
I want the Rails app to send a request to the Node.js app and only when the Node.js app returns, the Rails app shows the information to the user via UI (without the request being blocked).
This is the first time I need to do something like this and I'm not being able to know how. I was thinking that if I put the request in a queue (maybe redis pub sub) I could retrieve it using Node.js, process and return again. Would this work?
Also, how do I know which user made the request (I have to return the information processed by the node.js app to him)?
Thank you
To know which user made the request, pass in the user ID as an argument. If you have no User Id the other option to do this is via IPs but that will get complicated fast.
But what you described sounds like it would work.
If this is your first time, may I suggest looking into this screencast: http://railscasts.com/episodes/271-resque