I would like to integrate facebook in my actionscript application. I am using facebook actionscript api available from code.google.com.
I would like to know if there is any way to creating custom login dialog rather than using the default facebook login dialog as i want the user to just sign in to facebook rather than exploring the other fields like "Sign up" and "Forgot password"
I cant use the current api as websites use it for logging to facebook. It is open to sign ups exploring other languages.
I would like to prevent the whole thing by customizing the login dialog. Does facebook provide something for that? Or can it be done it in any way?
Any help appreciated.
Nope, never seen a way to customize it to that level where you can remove core functionality of their dialogs. The advanced auth dialog and the registration plugins can get customized more than the old one.
Related
I am trying to make an automated test of the Facebook login feature in our web application in Cypress. I would like to skip the visual input of credentials and rather provide them programatically.
I came across the cypress-social-login plugin - https://www.npmjs.com/package/cypress-social-logins
Does anyone have the experience specifically with the implementation of this plugin for Facebook login? Or did anyone manage to automate Facebook login without any plugin?
Another question is: for the plugin to work, I have to provide a login url fom my application. But my application doesn´t have a specific login url. It uses a fullscreen modal that contains a Facebook login button. Is there a way to modify the plugin to deal with this?
Meanwhile I accepted this fact. But I was successful by using another much simpler approach: First I go to facebook.com and log in there. Then I open my App and click the Facebook login button. In this way I can simulate the majority of users that are already signed in.
Unfortunately, when I run the tests on Lambdatest, Facebook won´t let me sign-in and tells me that I am misusing their services by going too fast :D
For now I am left by running tests locally.
I am trying to use the Facebook share dialog and, to do so, the Facebook JS SDK seems to need an app. So I create my app with the "website" type but the forms to get it validated ask me a lot of informations about the Facebook login (a description of the process, some screenshots,...), informations I can't give because I'm not using a Facebook login... and these fields are mandatory... you can see my problem now...
Is there a way to use the share dialog without configuring useless infos or without using an app to to so ?
You don't need to fill in App Details if you just are using the share dialog
I'm trying to add sharing for our mobile app and I have created the proper facebook app, custom open graph actions etc but we have decided against using facebook login/register for the moment. Apparently I cannot submit my app for approval to facebook if we're not using the facebook login.
Am I missing something or have we done something wrong?
It sounds like you are trying to submit your application to the Facebook App Center, which does require login integration per https://developers.facebook.com/docs/guides/appcenter/ - but this may not be what you're actually trying to do, which I'm guessing is just taking your app out of "sandbox" mode, which does not require anything more than a click.
As per the issue which you highlighted i guess most suitable option for you to create an "Access Token" for your "Facebook App" and using that "Access Token" you can override the login authentication.
Please have look on this article on "How to crate Access Token?": - http://techpost360.blogspot.com/2016/10/create-facebook-access-token.html
Hope it might help you to solve your issue.
I have implemented the sample application provided by DotNetOpenAuth as instructed here.
As you can see below, this is requiring that the user installs this facebook application.
I simply want to allow users to use their facebook login for my vanilla ASP.NET website.
Is there some way to prevent them from having to install a facebook application?
Update: Stackexchange Facebook login doesn't have an "install" button. It simply has a dialog requesting various permissions. This is much preferred in my case.
This will work until Facebook forces everybody to use the "Enhanced Auth Dialog"
You can fix this dialog by going into your advanced application settings:
Changing this setting will cause the dialog to appear as you suggested in your excellent question.
What's better?
Login Button
OAuth Dialog
I like the Login Button because it shows profile pictures of the user's friends who have already signed up for your application and it opens a dialog overlay instead redirecting to a new page as does the OAuth Dialog.
But, I think the OAuth Dialog is newer. Which should we use?
Also, the Login Button is XFBML. Apparently, Facebook is in the process of deprecating FBML. Does that mean XFBML is being deprecated too?
It isn't that one is better than the other - they are intended to accomplish different things.
The login button is used for external websites to allow Facebook-based social elements and community within that site. You can then add other plugins such as comments, the like button or the face pile to further integrate the Facebook social networking aspects, with the login button acting as the authentication mechanism.
The OAuth dialog is specifically for FB apps that run within the Facebook canvas, and allows you to request Graph API permissions from a user which will grant you access to various parts of their profile and additional channels of communication.
While Facebook is deprecating FBML, they are not including XFBML elements that support social plugins, such as the login button. See here for more info.
I think Daniel hit the nail on the head.
I have just started reading up on Facebook Development, and it seems they are providing a great set of tools to do very powerful things, but they aren't particularly explaining which bits do what.
I think you need to be sure of the difference between; a) creating a web app that will leverage the facebook api to enhance its functionality (i.e. using the login button to allow a user to login/create a profile on that website) and b) creating a Facebook app that makes use of the api to simplify development (i.e. authorize and authenticate a facebook user for an app request)
I don't think they have outlined that distinction very well throughout their documentation
The oAuth button is decidedly and absolutely better for a simple reason - it is documented and relatively stable.
The Login Button has nearly no documentation right now ( https://developers.facebook.com/docs/reference/plugins/login/ ), and the behavior has slightly changed several times.
The documentation for the login button is currently limited to how you can :
change the appearance [ width, show faces , rows ]
specify scope
specify a registration-url
For the last several months ( ~Jan - July 2012 ), the documentation has not included anything concerning the flow of information or status -- ie, what actually happens on a successful or failed login.
While there are answers to these questions on StackOverflow , and mentions of other parameters that seem to work when passed in, Facebook does not mention or document any of this functionality at all, so it is essentially use at your own risk. The LoginButton is essentially a black box of mystery, that people just seem to have working thanks to undocumented features, and with functionality that will change/cease on random weekly updates.
tl;dr - stay the f(*& away from the Login Button and just use oAuth