All geek questions in one place

FB.login - the same application identifier with multiple domains

So, we want to start using FB.login for our sites, and not for redirecting a full page, because it looks better. But there is one problem. We are currently using domain aliases to solve the problem with multiple domains / single applications. That is, when a user logs on to www.domain.com we transparently add the suffix at the FB Handshake ID (for example, www.domain.com.master.com). This works well for this use case, but it looks like something similar is not happening with FB.login. Has anyone done something similar to get FB.login to work with multiple domains with a single application identifier?

Thanks!

+4
source share
3 answers

You must specify all domains in the "Domain Domain" field in the "Basic Settings" application, this will allow you to transparently use the Facebook JavaScript SDK to authorize your users.

+1
source

Please note that you can specify several subdomains, but they can belong to only one domain. This is because it must match the URL on the website using Facebook Login> Site URL.

This is a problem for me when I develop applications for Facebook with several channel dialogs that require redirecting URLs to different domains.

+1
source

We used the same web game application identifier that was accessible through the facebook canvas and simple fb.login - for example, you can use the website and login using your username and password. Or you can log in using your facebook user password (for example, f connect) Or you can access our application in the canvas as a facebook application.

Facebook sent us an email saying it wasn’t allowed — using the same iD application to access the same application in different ways. We had to change the application identifier. Now it works great.

Hope that helps one way or another and is related to the original request.

0
source

Source: https://habr.com/ru/post/1389733/

More articles:


All Articles