I've been trying to get this to work for a while, but I've apparently missed something.
All I want is to have the latest 3 or so posts from my clients Facebook page to populate and animate in a screensaver that I am building using Flash (AS3).
So far, every time I try to bring anything in, it requires a complete oAuth login and account link, but it's only a one way exchange (read-only, absolutely no writing, posting or even linking, since it's a screensaver) I'm not even sure the client wants pictures or anything.
I am currently trying to use the facebook-actionscript-api, but there isn't an option for the "App Login" type of Authentication that would solve most of my problems.
I'm at wits end and about to have to tell my client it can't be done. At least they'll always have twitter...
I don't think it is possible to get facebook feeds without an accesstoken (even if they are public). So I guess you need to define an app within Facebook and add login stuff to your app so users can give permission to your app for basic access.
Maybe this article offers some help: http://www.adobe.com/devnet/facebook/articles/flex_fbgraph_pt1.html
Related
I have an packaged app in the Chrome Web Store that I'd like to transition from a paid app to a free one with in app purchases. I need to be able to detect if the current user had paid for the app previously.
To be able to use the licensing API, I need the current user's OpenID URL. I was able to get this to work using chrome.identity and a popup dialog that the user has to authorize. But it is a bad experience and kind of a scary dialog.
For hosted apps, it's possible to get the user's OpenID URL without any user interaction or authorization. (see How to skip the OpenID approval screen). It would be fantastic if somebody knows how to make this work without user interaction for packaged apps.
I've detailed some of the approaches I've tried on this chromium-apps thread. I suspect it may be possible to do this with chrome.identity.launchWebAuthFlow but I wasn't able to discover the exact incantation of parameters to google's oauth/openid endpoints to make this happen silently.
I think you need to refer to this Link1 Parameters
this parameters are different techniques using that you can do this task..
also To bypass the Login/approval screen refer this link2
Here in the section How to skip the OpenID approval screen the details are explained which you can use..
And In case of packaged app this should ask for permanent permission that will help in OAuth throughout the life of app..
Client Library JavaScript Based
Authentication using Library
After your comment I thought this you can bind in your app.!!
Let me know what works for you..
I'm sure this is something blindingly obvious, but I can't work it out.
I've added an admin and a tester user to my app (and I mean they're real people as opposed to the generated random named user that FB offers) but after a couple of weeks they're still listed as '(pending)' and they're unable to login to the web page that I've written using their Facebook account. OAuth responds with an error:
Sorry, this feature isn't available right now: An error occurred while processing this request. Please try again later.
I appear to be able to login just fine and can test the [currently] limited functions.
Our web page is right at the beginning of development but it's now at the stage where I'd like real people to mess around on the page and give me feedback.
The two users haven't received any messages - I sort of expected they'd get something in their inbox asking to confirm their role with the app.
So how do I go about getting real people to be test users? Have I missed the point of the test user role?
As of this writing (things change), have the Facebook user go to https://developers.facebook.com/requests/
They will need to be logged in to Facebook.
There should be listed one or more pending requests that they will need to confirm. If the Confirm button(s) is disabled, they may need to register as a Facebook Developer before the Confirm buttons are enabled.
I am not sure if anyone has ran into the problem but it is really bugging me and affecting our uploading from our iPad to facebook.
I have a local server running XAMMP with a gallery of images displayed via a local web page. These images are from our Photobooths and automatically get added into the gallery when a photo is taken in the booth.
These can then be accessed on the local network via the iPad. Users can then login to facebook and share this images.
Because this is a shared iPad being used by multiple users, is there any way of getting users to login without having to answer security questions?? It used to be fine but now Facebook says the login is suspicious as it does to recognise the device.
I have created an App to post the photos to facebook through the Facebook Development site and it works perfectly from my account and many users, but some seem to get the suspicious login attempt and have to identify friends and date of birth etc.
Is there a correct way to do this?
Thank you Richard.
Is there a correct way to do this?
What you are experiencing is the “correct” way.
Facebook offers this as a security feature – a user can add his devices to his list of “known” devices, from which he will be able to login straight away, and have to answer additional security questions when logging in from a different, “unknown” device.
If users have this feature enabled, they should not be surprised by this happening in your scneario. It’s what they explicitly want, and they’re getting it.
So you should in no way try to mess with that, just because you might think this to be “uncool” or a “nuisance” – it’s not, it’s a feature offering extended security that the user wants and has explicitly chosen.
I have a website that's working with Facebook Connect (or Facebook for Websites as I think it's called now). When a user first comes to the site he's able ot browse around and do some simple things without any integration with Facebook. If he wants to perform some advanced operations, we need him logged into Facebook and to authorize our app to grab some very basic information about him. We're trying to be good corporate citizens by letting him get a taste of the site without forcing him to be logged in and authorize.
To do this, we have a Login button that he needs to push before performing advanced functions. When it's pushed we call https://www.facebook.com/dialog/oauth, etc. to get things set up.
This system works fine except for one thing. IF he is already logged into Facebook AND IF he has already authorized our app, he should just be frictionlessly logged in when he goes to the webapp. But, I can't see how to do this.
Sure, I can call https://www.facebook.com/dialog/oauth when he starts the webapp, and if the conditions are right, things work great. But if the conditions aren't right, then he's presented with a bunch of things to do that I don't want to task him with just yet.
Surely there's a way around this. How can I frictionlessly allow my users to authenticate through Facebook with the stipulation that if any of the conditions are wrong, just abort the whole process without showing the user anything?
Before you display a login button for the user, call FB.getLoginStatus() to see if they're already logged in or not.
I have seen many web apps supporting Facebook Connect...
But when i login through those apps sometimes the authentication is successful but nothing is returned to the app and the login page just goes to a blank page in that new windows and stops... The whole process fails... And this has not occurred once but many times...
So my question is:
Is Facebook Connect a good solution to use in apps or should i use something like Google Login or Twitter Login or OpenID or just a simple password based login or all of the things and let users choose what they want?
And if your answer is app the solutions then wont my database become messy and the app slower because it has look for more data now?
I know it depends on various factors but I just want your opinion, what would u choose and why?
Supporting Facebook connect as login function make sense only if your app has something to deal with Facebook (which is the most of our app today ;-)).
The behave of some app when sucessfully Authenticated and then Authorized is up to these app.
FB login give you all the tools to build you own user experience.
The things become a bit more difficult when you want to introduce FBConnect within already existing login base, while you have to find a way to bind the Identified FB user with your user account.