Currently , we do have many sites with different domains. Right now, we have to create a new FB app using developer account for each and every website manually in order to support FB login. Is there a way to automate this FB app creation process or to use same FB app for multiple domains?
I have the Facebook app that is running perfectly fine. I just launched the new company and i would like to use the same Facebook approved app that works for both companies. Is there anyone know how to manage the two different domains in the same app.
Note I already add the domains in the Valid OAuth Redirect URls but how we can add two separate logo in the same developer app account.
Hope you understand what I mean.
Wahab
I have more than few clients that would like to add facebook connect to their landing pages (managed by me). They are too many and not enough tech-savvy to manually create ad appid for each of them.
So my only solution is to usa my own appid to add facebook connect to all my clients websites, but as far as I know, Facebook doesn't allow to simply use the same appid on any domain.
How can I solve this? I can't find any documentation to solve my issue. Does anyone have a direction for me?
This has been discussed a couple o’ times before already – but I mostly commented on earlier questions, so let me write the whole thing up as a proper answer, for future reference.
[paraphrased] Multiple-client Facebook login via one single app id
Does anyone have a direction for me?
You probably rather don’t want to do that.
It is not really possible to run one simple app one multiple different domains.
As a workaround for only a few domains, people used to specify different domains for the different platforms – Website, Page Tab or Canvas App, plus Mobile alternative for Canvas – without actually using any of those platforms besides Website, which made the app usable on multiple domains as a website app. But since Facebook introduced their login/permission review process¹, you can’t do that any more – they expect you to present actual functionality on all platforms you have configured in your app.
You can kind-off use one single app for login on multiple domains – if you are willing to use only the server-side login flow, and to redirect users to one “main” domain (that gets specified as the app domain in the app settings) to login, and then from there back to the origin domain.
But this has several drawbacks:
It’s not what you’d call a “white label” solution. If your clients expect it to look as if users where logging in via “their” app, it should stay on their domain. Individual branding, in regard to stuff such as app name, app logo that shows in the login dialog, etc., would also not be possible. Additionally, app attribution – the link that shows up under content shared/posted via the app – would only link users back to the main domain, and not to your customer’s.
You would not be able to use the JS SDK for client-side API requests, or even just to embed it to render any of the FB social plugins that require an app id – the SDK checks what domain it is “running on”, and can not be tricked to accept a domain that is not specified in the app settings.
There could be privacy issues. An over-exaggerated example: Just because I as the app user decided to share my photos or videos I have on Facebook with your customer Our-Holy-Mother-of-Christ-Bakery.com, does not necessarily mean I want to share them with your other customer, amateurs-doing-all-kinds-of-nasty-stuff.xxx as well – but if they shared an app id for login purposes, I automatically would. Have fun writin’ the Privacy Policy (which is mandatory if you use FB login functionality, and FB also automatically checks if your app has got one) for that scenario ;-)
Finally, and most importantly: All your customers would be “sitting in the same boat.” If one of them, or in turn their website users, would publish spam via your app id, so that Facebook blocks it, login would not work any more for all of your customer’s websites. And if you decide only then, that setting up an individual app for each of your customers would be the better way to go, they would not be able to recognize their existing users any more, because of user ids being app-scoped since API v2.0 was introduced – so if users logged into this new app, that app would see a totally different user id. (And to rely on an email address as an identifier is risky, too, because you will not get one from the API for every user; for example if they registered using their mobile device.)
Edit: Plus, app/domain insights, as luschn mentioned in his answer.
¹ Yes, the review process has made it more laborious to set up multiple apps for multiple clients. But for apps that do the same stuff/use the same permissions in the same manner, you can refer to an earlier successfully reviewed app id to speed up the process a little. Also, screenshots of how f.e. posts made via the app look on timeline, and what UI components are used, as well as screencasts that you include in your submission could probably be used with little to no alteration.
Apps are not meant be used on several different domains, you will have to create a new App for each domain, i´m afraid. You can use the different platforms in the App settings to use different domains, but there are only a few so it´s pointless. Just create some screenshots and a tutorial for your clients, that´s how it is usually done.
Btw, it would be weird to authorize an App on a website, and the same App would allow you to be authorized on all other client websites. Also, insights are per App, so your clients may want to see their own insights and not the global insights of all domains together.
Many is not defined but i think for being a smart developer you need to create new app_ids for every project you need to use facebook connect. Just my opinion. It also allows you to monitor alot of stuff.
I've spent the past few hours trying to figure this out but can't find anything.
Basically I've setup a website for a music festival, I'm trying to integrate Facebook with the site and whenever I create an app it keeps creating it under my personal account.
I am setup as an admin under the music site's Facebook but I still can't figure out how to create an app just for that music site completely separate from my personal account.
Anytime I try to access the developer section using the account it gives me this error:
http://smyl.es/ss/001.png
This is by design.
I'm assuming the music site is a Facebook page?
While you can log in and use Facebook as the page, rather than yourself, Facebook apps are always owned by a real Facebook user, not a page. So you either need to create the app yourself, or have someone else create the app and add you as a developer.
From what I understand, everything you do is associated with your personal account as the developer. However, you aren't supposed to be putting it on your personal page. As the developer, whenever I do anything it shows up in my personal account because I am set up as the developer and admin of all my pages. That's how Facebook wants it. Before, people were setting up different accounts for a business profile and it ended up with lots of businesses as personal accounts instead of business pages with an admin user.
Whenever I do anything with Facebook I have everything available to all the pages, but only one is actually using the app or whatever it is. Does anyone see anything different?
I am looking for a way to make a Facebook app that signs the user up to an external website when the user installs the app and accepts/allows the app to share user information. I have been looking for a while, but still not sure what the main steps would look like. The external website was built using SocialEngine.net.
Then you want to use the registration plug in:
See https://developers.facebook.com/docs/plugins/registration