facebook-oauth

What am I doing wrong in localhost Facebook app development?

由 夙愿已清 提交于 2019-11-28 08:40:38
App Domains: localhost Website with Facebook login: http://localhost/auth I go to http://localhost/auth/ and in my Chrome developer console I see the error: Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains. I do a view-source to see the following: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text

OAuth Error: This IP can't make requests for that application

由 て烟熏妆下的殇ゞ 提交于 2019-11-28 08:25:32
I just started to get random This IP can't make requests for that application. errors with my app. My server's IP address is on my whitelist from my app's settings, and it was working perfectly, but I randomly started to get this error. I've checked my server's IP (even though I already know it's static), I've removed all the entries in the whitelist, but none seem to work. Weird enough, I can test the exact same code from my home and it works! What could be the cause of the problem? This wasn't happening even a few minutes ago, but now I'm getting an error at my server. Thanks, Can. UPDATE :

Facebook iframe app being redirected out of canvas after user authorization

由 亡梦爱人 提交于 2019-11-27 17:01:45
问题 My facebook app is being redirected to the canvas url (http://my-domain/app) after the user has authorized the app. The sequence of steps is described below: 1) A new user opens the app in canvas and is redirected to oauth permissions dialog via Javascript redirection 2) Once the user has authorized the app, the redirect_uri of the app is called and I get the access token which I save in session 3) I also get the user id of the authorized user and save it to session 4) When I redirect it to

Java example of how to log in to Google App Engine with a Facebook account using OAuth

由 半城伤御伤魂 提交于 2019-11-27 16:56:03
I searched a lot, read many blogs, articles, tutorials, but until now did not get a working example of using a Facebook account to log in to my application. I know that I have to use OAuth, get tokens, authorizations, etc... Can anyone share an example? Here is how I do it on App Engine: Step 1) Register an "app" on Facebook (cf. https://developers.facebook.com/ ). You give Facebook a name for the app and a url. The url you register is the url to the page (jsp or servlet) that you want to handle the login. From the registration you get two strings, an "app ID" and an "app secret" (the latter

Get application id from user access token (or verify the source application for a token)

由 泪湿孤枕 提交于 2019-11-27 10:26:00
I found this question , which has an answer, but facebook changed the token format since then, now it is something like: AAACEdEose0cBACgUMGMCRi9qVbqO3u7mdATQzg[more funny letters]ig8b3uss9WrhGZBYjr20rnJu263BAZDZD In short, you cannot infer anything from it. I also found the access token debugger , which shows the information I am looking for if you paste a token in, which is nice, but does not help me do it programmatically. Point is, if someone gets a token for a user, he can use it to access the graph, which is what I do in my application - I want to be sure that people are forwarding the

Facebook 60 day access token and Deprecated Offline_Access

由 江枫思渺然 提交于 2019-11-27 08:46:46
Facebook's "Deprecated Offline Access" doc ( http://developers.facebook.com/docs/offline-access-deprecation/ ) states the following: *Server-side OAuth Developers If the access_token is generated from a server-side OAuth call, the resulting access_token will have the longer expiration time. If the call is made while there is still a valid access_token for that user, the returned access_token from this second call may be the same or may have changed, but in either case the expiration time will have been reset. Again, calling this multiple times during the same day will result only in the first

Java example of how to log in to Google App Engine with a Facebook account using OAuth

由 那年仲夏 提交于 2019-11-27 04:09:59
问题 I searched a lot, read many blogs, articles, tutorials, but until now did not get a working example of using a Facebook account to log in to my application. I know that I have to use OAuth, get tokens, authorizations, etc... Can anyone share an example? 回答1: Here is how I do it on App Engine: Step 1) Register an "app" on Facebook (cf. https://developers.facebook.com/ ). You give Facebook a name for the app and a url. The url you register is the url to the page (jsp or servlet) that you want

What am I doing wrong in localhost Facebook app development?

由 让人想犯罪 __ 提交于 2019-11-27 02:27:23
问题 App Domains: localhost Website with Facebook login: http://localhost/auth I go to http://localhost/auth/ and in my Chrome developer console I see the error: Given URL is not allowed by the Application configuration.: One or more of the given URLs is not allowed by the App's settings. It must match the Website URL or Canvas URL, or the domain must be a subdomain of one of the App's domains. I do a view-source to see the following: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"

Facebook 60 day access token and Deprecated Offline_Access

由 元气小坏坏 提交于 2019-11-26 14:17:32
问题 Facebook's "Deprecated Offline Access" doc (http://developers.facebook.com/docs/offline-access-deprecation/) states the following: *Server-side OAuth Developers If the access_token is generated from a server-side OAuth call, the resulting access_token will have the longer expiration time. If the call is made while there is still a valid access_token for that user, the returned access_token from this second call may be the same or may have changed, but in either case the expiration time will

How to extend access token validity since offline_access deprecation

由 亡梦爱人 提交于 2019-11-26 01:44:34
问题 Since the offline_access Permission is deprecated in Facebook\'s Authentication flow, we have problem geting the so called long lived access tokens without that permission. In Facebook\'s document about the deprecation it says, that server side OAuth generated access tokens will be long lived, but they are not. Am I missing something? Some setting in app settings? Some special code I need to use to extend expiration time of access tokens? As I understand the documentation, for server side
订阅 facebook-oauth