I have a working php code which lets users login through Google Api.
The problem is, this code requires users to become Google Plus users.
I use the latest api located at http://code.google.com/p/google-api-php-client/downloads/list and still couldn't find out if I can use the same service for people who do not have and do not want to activate Google "plus".
update: I understand that this might be a 3rd party api question and I also think that this is a question about a popular 3rd party api and this question and it's answers may still help many people out there.
answer of the question: for quick reference, the answer is *Google_Oauth2Service* class
You can use Google OAuth as a mechanism to authenticate users without requiring that those Google users have activated Google+ accounts. See Using OAuth 2.0 for login. This approach relies on requesting the user's identity via the userinfo.profile or userinfo.email OAuth scopes.
You get advanced functionality and social capabilities if you use Google+ Sign-In, and if your users opt for that option, they will be prompted to upgrade their Google account. This approach uses the plus.login OAuth scope, which gets you identity information in addition to other API methods that can be called.
Choosing the approach that works for your app and audience is up to you.
As of june 2015, you have to use the google+ API to set up the sign-in (Other methods were deprecated).
If you want your user to sign-in without a google+ account, you need to specify "profile" instead of "https://www.googleapis.com/auth/plus.login" as the scope as explained here
Related
I have an api, which has a regular email password login. But I want to add facebook logins.
Do I need an app registered on facebook?
Do I need to force users to register using facebook, or just link their facebook account to their account and use it as a form of auth.
How does this tie into mobile apps? Given I am writing the API, what info does the client provide for a facebook login and what do I need to store?
There is a plethora of info out there and I am not sure where to start. I am writing an API, but I am not sure how much work my API has to do and how much the client just has to deal directly with facebook. Any specific guides tailored more toward what I am doing would be great.
A simple library called HybridAuth available that takes the pain out of building a social login feature.
Here is a very detailed tutorial from Sitepoint.
I am answering this even though this question in 1 year old, because this is visible on google search top 3 links. It might help someone who stumble upon this like I did few months ago.
I have signed a NDA with yodlee and i have got all the SDK files(java,jar and other related docs).
I am a PHP Programmer and from my understanding:
Yodlee is like an engine (almost like Twitter or Facebook) and we need to leverage the API to build different apps
The documents I have gone through is not with good-sufficient information.
They use SOAP-API and I need to use this API.
I have surfed the net for days, and finally posting a question here.
My Question is very simple
I have to register a user from my php-form to yodlee using soap-api -> Is this possible
If No, is it possible to login from my web-portal to yodlee and access the fin.apps.?
# 1 is possible. Other clients have done it. You just have to invoke the web services operations from php. We have php sample code.talk to the sales representative about getting access to sample apps plus Yodlee SDK developer forum.
# 2 is not possible.
The Google Identity Toolkit is awesome. So clean and easy to set up! Trouble is, it forces you to use its UI, which isn't working for me. Is there anything else out there that will let the visitor click a GMAIL or YAHOO Mail icon to trigger an OpenID (or oAuth2) request, without hijacking the interface?
I've already implemented Facebook Logins in my site, which lets me customize the sign-in button however I want. For example, here's my current sign-in menu (with PHP/AJAX/MySQL site authentication for those who don't want to use their Facebook/etc. account to sign in):
Clicking FACEBOOK triggers the Facebook JS SDK for the login. Simple enough. I just want a GMAIL logo and YAHOO logo below it.
Any suggestions?
If you want to avoid the UI of a high level library, you're going to have to use a lower level library. In particular, you're going to need an OAuth 2 library. There's not that many of them (surprisingly), but your best bet is likely going to be the one authored by google: http://code.google.com/p/google-api-php-client/wiki/OAuth2
If you're looking for a solution that allows you to leverage all of the APIs for the major ID providers, you might want to test out Janrain Engage.
Here's a quick lowdown on our Engage API endpoints (specifically, auth_info), for social authentication:
http://developers.janrain.com/documentation/api/#Engage
You can have complete control over the UI and display just Google and Yahoo.
http://janrain.com/products/engage/ (for marketing-ese)
I am developing an advertisement site in PHP, the user can only list there products by logging in using there account in the site. Also i need to have another option for users to login into the website using there Facebook account and hence advertise about their products. How can i implement? Do i need to create any application instance in FB for this? I am looking forward for valuable suggestions.
Create an app.
Look into authentication, and see which method (server-side vs. client-side) fits you.
Once you've implemented that, you can make graph api calls. https://graph.facebook.com/me gives you the user's basic details
Good luck.
In my project all the Gmail users can access my application. So I referred Google API, The suggest me to use OpenID / OAuth.
Could you say which one is better.
I referred many no. of tutorials regarding oAuth, but none of them satisfied me.
So Please advice, the simple method to achieve this.
I would recommend the OpenID+OAuth Hybrid protocol as it lets you combine an OpenID request with an OAuth authentication request. This extension is useful you if require the use both OpenID and OAuth, particularly in that it simplifies the process for users by requesting their approval once instead of twice.
It means you can use google APIs aswell as pull back the user's information. This is a very interesting article on the differences and similarities of oAuth + openID.
However, if you don't need to use any of the google API's and just need to pull back user info have a look at LightOpenID - it is really easy to use. and has an out-the-box example with Google OpenID