I am somewhat new to using the facebook c# sdk. I'm trying to add the ability to add login capabilities to my website using facebook. However, I don't seem to be able to achieve the same login auth dialog look that other sites give.
When I view other sites that allow login via facebook (i.e. Bing, Pinterest), their auth dialog screens look exactly like what I am looking for. That is logo, followed by title. Then description, then the "By proceeding you are agreeing to...." line. Then below in the darker gray shaded area is the friends strip, and the Log In and Cancel Buttons on the lower right hand side. For my site, I am getting an auth dialog with an "Okay, go to app" button in the upper right hand corner of the auth window. It does not show the strip of friends that use the app. and there is no "Login" and "Cancel" button at the bottom.
How can I achieve the desired look? I have tried disabling the Enhanced Auth Dialog in the advanced settings of my app, but this generates an auth dialog that is even further from the desired result.
I have compared the url strings that I am using to do the auth, with these other sites and they are exactly the same (obviously using my own appid, and permission requested). So that tells me it must be something on the app setup side on facebook. I just can't seem to determine what options need to be set to cause my app to display a login screen similar to the other sites I have mentioned.
Any help would be greatly appreciated.
Thanks.
Could it be that you haven't opted in to the "Enhanced Auth Dialog"? Go to:
https://developers.facebook.com/apps/[your-app-id]/advanced
And make sure "Enhanced Auth Dialog" is set to active.
Related
Notice how clicking on the Instagram App entry of a facebook search sends the user directly to instagram's website. How is this accomplished?
There appears to be a somewhat related question (with an accepted answer) here: Facebook App: Make the landing page redirect to a URL? However, it isn't clear this is the correct way to do it, as it doesn't provide the same user experience.
Invoking such an implementation will first send the user to what would be a facebook app page with an iframe. Then that iframe (with the suggested redirect code) invokes the redirect. This is quick, but still obvious to the user, and clearly different. Not to mention, it may also go against Facebook's terms (not sure though).
Bottom line is, how does one configure a facebook app link to behave as the Instagram app link?
(Note, I would have simply added this comment to the referenced question, but it seems I don't have the required rep points yet).
in the https://developers.facebook.com/apps - go to "edit app", and in the Settings -> Basic, choose only "Website with Facebook Login" (and you'll see a green V).
Now go to "App Center" in the left bar - fill all the necessary forms and hit submit.
and then go to: https://www.facebook.com/appcenter/YOUR_APP_NAME
I might be wrong but here is my two cents;
Go to the App Developer page on Facebook (https://developers.facebook.com/apps/)
Create a new application and on Settings -> Basic enter your website URL under Website (after you clicked on it)
Then goto Settings -> Advanced and at the bottom of the page there is an button which says Create Facebook Page click on it and once someone clicks on your Facebook page they should be redirected to your website.
I have Janrain Engage for a site with three providers (Facebook, Google, Yahoo)
If a users authenticates say via Facebook on my site and then comes back to my site, instead of showing the three login options it shows only Facebook Icon and Sign In As NAME. To get to the screen with the three options you have to press "Switch Accounts".
Is there anyway for JanRain not to do this? Not to only show the login option you previously used, but instead show all of them?
Add the following to your block of widget settings (assuming you're using the newer widget):
janrain.settings.noReturnExperience = true;
I am trying to use new enhanced auth dialog instead of old one in a new application,
I want to first of all display a page with a message to the user, then he can click on a button and then he have the enhanced auth dialog.
My worries are when i set up my new application, the auth dialog v2 is displayed and then if the user accept permissions, then he is redirected to my home.php.
Is it possible to use enhanced auth dialog but first of all displaying a page which inform about the application?
Thanks! :-)
Yes it is possible to first display a page to the user before putting up the auth dialog. I have a current production app that does just that.
In your app, have a connect button of your own making that you display to the user when they are not connected to Facebook.
When a user clicks it, redirect to the page you want to show them with the special wording.
On that special page, have the real facebook login button (or a button/link that fires off FB.login())
Well, I have found the answer.
If you don't want that Facebook display the enhanced auth dialog before your application, but do it manually, when you want,
in your app settings, in "auth dialog" tab, don't write anyting in "Authenticated Referrals" !
And that's all :-)
I tried to create my first app.
I went to https://developers.facebook.com/ and clicked on 'applications'.
Then facebook redirected me to my facebook page. There was NO button to '+add an application' and no form to ask me if I needed 'something' to create the application.
I added a valid credit card because it's mandatory to get a 'developer' status.
How I can add an application to facebook. Is there a way to ask their tech department?
(edited)->
Also if I click on https://developers.facebook.com/apps it redirects me to my facebook page WITHOUT a window to 'Request for permision'
<-(edited)
Here you will have a button to add New App, a popup should appear to write the New App's name. I can see in your post you don't get this popup, but it is where you need to go. So try using this link on your Personal Account not your pages account, just like DMCS is saying.
Here you should get a couple of more links, and there's a how to link that might help.
<---edit--->
Here you can find a fast track to build a facebook app. Not sure if it's what you want, but it might help in some parts of the process.
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