For Facebook/Google SSO (single-sgin-on),
the normal procedure is to create a separate FB developer app and
get the key pairs & integrate with the application.
If white labeling is allowed as below:
client1.com points to client1.ourproduct.com
client2.com points to client2.ourproduct.com
client3.com points to client3.ourproduct.com
Is there any better approach to avoid creating FB developer
apps for each customer/client and integrate with the application?
I mean, is there any way to manage with a single developer app
and manage with this esp when white labeling is allowed?
Kindly suggest.
Related
I hope you can direct me with my query.
I wish to create my own authentication method for users in my Google Apps for Work account. Currently I am using built in Google Authentication, however I wish to build my own authentication method in PHP, Phyton or .NET; language doesn't matter really. So I want users to go to the page I will create, then they will need to pass authentication and be logged to Google Apps.
I know SSO is the way to do it but after my research I found very little about how to achieve it with Google Apps. I mean there is tones of third party platforms like OneLogin etc but I would like to have something I build myself. Ideally I would like to have some examples of SSO which works with GAFW so I could figure out the rest myself. I read somewhere that building own SSO portal it's not a piece of cake and also found an article that you can create something based on oAuth2.0 instead. So tried research about oAuth2.0 but all documentation I found is about authenticating to the application that I build using Google Apps Credentials, where I want the opposite; to be able to access Google Apps using the app that I build.
Hope someone could direct me to some examples or documentation or explain the process of learning curve to get my head around this project of building SSO for GAFW.
If you want to write your own Auth system and become the Identity Provider (IdP), you need to use SAML as that is the only supported method for now.
Here are the step by step instructions
I created an application as part of a university project that searches using web APIs. Google+ is one of the APIs considered.
Now I am trying to evaluate this application against what other search tools offer. In the evaluation, I ask the user to create a google plus account and then try to find it using the search engine example.com and then try our tool.
The problem I am having is that when I create a google plus profile, I can not find it immediately using "Google+ API people search". Is there a way to tell the API to consider recently created profiles or any other solution to this.
No. Google+ is a large application and things can take time to process by various other systems.
My wife is starting her local business, and I would like to develop a booking application that users can use to book appointments with. Is this feasible using the facebook development tools? I tried to overview the documentation at https://developers.facebook.com but I came out with no clear answer.
What is a Facebook app?
In layman terms, it's just a window to your actual app with a bonus that you can use Facebook's social data with it. So, yes! Basically, you can pretty much do anything with it. Plus, if you are looking forward to create an app for a local business, I would recommend taking a look at page tabs from here.
Here is how a Facebook app works:
You create an app on your server.
You give it's url to Facebook (called the canvas url).
You specify the dimensions.
And that's it! Your app is up and running!
I freelance now and I am wanting to set up a Facebook account so I can create multiple apps for different clients under this account, then become admin and roll out the app totheir page.
Does anyone else do this and if so how best is it to set up from the outset as I will need to test without the public seeing etc.
Yes - I do this frequently...
Placing your application in sandbox_mode will ensure that only the people who are allowed to see the application have access to it.
You can also add your applications to your own un-published Facebook page, that way no one will be able to search for your page or application either.
A mixture of sandbox_mode and an un-published page should be the safe way to go. Check out the Application Security page in Facebook's documentation for exact explanations of sandbox_mode and the roles you can give users in your application.
Im new to facebook applications. I recently created a webapp that consisted of html & php. But recently Ive decided that integrating my webapp within facebook would be useful. Any tips on where to start? Ive looked over developers.facebook.com and im confused. It appears they are in the process of updating. Ive come across a few guides but there from a few years ago. This app will run completely within facebook and im probably gonna have to rewrite all the code. Any guides or suggestions?
Thanks!
You didn't specify the programming language you're using but if you're developing asp, start by looking into Facebook c# sdk here: http://facebooksdk.codeplex.com/
If you're using any other language (i.e. php), try looking into respective software dev. kits (i.e. facebook php sdk). They will facilitate your job in comparison to starting raw development all by yourself.
Tim, if you want to get into the business of working with Facebook, you need to know right away that they are always in the process of updating. That being said, you should learn some Facebook terminology so you can do more research and figure out what you want to do.
Applications that run within the Facebook interface are called Canvas Apps. Your application is hosted on your own server, and Facebook simply adds an iframe in their UI that points to your app's URL.
Another way to go to create a webapp that uses your own design, but still utilizes a single sign-on system from Facebook. This used to be called a Connect App but now they don't really have a name for it. Basically, you can use Facebook's authorization system to pull Facebook user data into your own database, which basically eliminates the need for a registration page. The authorization system prompts the user to allow your app to get specific data about them - once they authorize it, your app has access to do whatever the user gave it permission to do.
The best document to wrap your brain around is about authentication: http://developers.facebook.com/docs/authentication/
Give that a whirl, and good luck!