hello.js

A client-side Javascript SDK for authenticating with OAuth2 (and OAuth1 with a oauth proxy) web services and querying their REST API's. HelloJS Standardizes paths and responses to common API's like Google Data Services, Facebook Graph and Windows Live Connect. Its modular so that list is growing. No more spaghetti code!

...I did not understand any of that

Dont worry, here's a demo which illustrates what HelloJS can do. Connect a user through a service they belong too, e.g.

Hey, we got your details, test done! Choose another service or checkout what else you can do

Features

Looking for more? HelloJS supports a lot more actions than just getting the users profile. Like, matching users with a users social friends list, sharing events with the users social streams, accessing and playing around with a users photos. Lets see if these whet your appetite ...

• Items marked with a ✓ are fully working and can be tested here.
• Items marked with a ✗ aren't provided by the provider at this time.
• Blank items are work in progress, but there is good evidence that they can be done.
• Anything not listed i have no knowledge of and would appreciate input.

Install

Compiled source, which combines all the modules can be obtained from Github, and source files can be found in Source.

Bower Package

	# Install the package manager, bower
	npm install bower

	# Install hello
	bower install hello

The Bower package shall install the aforementioned "/src" and "/dist" directories. The "/src" directory provides individual modules which can be packaged as desired.

Note: Some services require OAuth1 or server-side OAuth2 authorization. In such case HelloJS communicates with an OAuth Proxy.

Quick Start

Quick start shows you how to go from zero to loading in the name and picture of a user, like in the demo above.

1. Register your app domain
2. Include hello.js script
3. Create the signin buttons
4. Setup listener for login and retrieve user info.
5. Initiate the client_ids and all listeners

1. Register

Register your application with atleast one of the following networks. Ensure you register the correct domain as they can be quite picky

• FaceBook
• Windows Live
• Google +

2. Include Hello.js script in your page

3. Create the signin buttons

Just add onclick events to call hello( network ).login(). Style your buttons as you like, i've used zocial css, but there are many other icon sets and fonts

4. Add listeners for the user login

Lets define a simple function, which will load a user profile into the page after they signin and on subsequent page refreshes. Below is our event listener which will listen for a change in the authentication event and make an API call for data.

5. Configure hello.js with your client_id's and initiate all listeners

Now let's wire it up with our registration detail obtained in step 1. By passing a [key:value, ...] list into the hello.init function. e.g....

That's it. The code above actually powers the demo at the start so, no excuses.

Core Methods

hello.init()

Initiate the environment. And add the application credentials

hello.init( {facebook: id, windows: id, google: id, .... } )

Example:

	hello.init({
		facebook : '359288236870',
		windows : '000000004403AD10'
	});

hello.login()

If a network string is provided: A consent window to authenticate with that network will be initiated. Else if no network is provided a prompt to select one of the networks will open. A callback will be executed if the user authenticates and or cancels the authentication flow.

hello.login( [network] [,options] [, callback() ] )

Examples:

	hello( "facebook" ).login( function(){
		alert("You are signed in to Facebook");
	});

hello.logout()

Remove all sessions or individual sessions.

hello.logout( [network] [, callback() ] )

Example:

	hello( "facebook" ).logout(function(){
		alert("Signed out");
	});

hello.getAuthResponse()

Get the current status of the session, this is an synchronous request and does not validate any session cookies which may have expired.

hello.getAuthResponse( network );

Examples:

	var online = function(session){
		var current_time = (new Date()).getTime() / 1000;
		return session && session.access_token && session.expires > current_time;
	};

	var fb = hello( "facebook" ).getAuthResponse();
	var wl = hello( "windows" ).getAuthResponse();

	alert(( online(fb) ? "Signed":"Not signed") + " into FaceBook, " + ( online(wl) ? "Signed":"Not signed")+" into Windows Live");

hello.api()

Make calls to the API for getting and posting data

hello.api( [ path ], [ method ], [ data ], [ callback(json) ] )

Examples:

	hello( "facebook" ).api("me").success(function(json){
		alert("Your name is "+ json.name);
	}).error(function(){
		alert("Whoops!");
	});

Event subscription

hello.on()

Bind a callback to an event. An event maybe triggered by a change in user state or a change in some detail.

hello.on( event, callback );

Example:

	var sessionstart =  function(){
		alert("Session has started");
	};
	hello.on("auth.login",sessionstart);

hello.off()

Remove a callback, both event name and function must exist

hello.off( event, callback );

	hello.off("auth.login",sessionstart);

Misc

Pagination, Limit and Next Page

A convenient function to get the `next` resultset is provided in the second parameter of any GET callback. Calling this function recreates the request with the original parameters and event listeners. Albeit the original path is augmented with the parameters defined in the paging.next property.

	hello( "facebook" ).api( "me/friends", {limit: 1} ).success( function( json, next ){
		if( next ){
			if( confirm( "Got friend "+ json.data[0].name + ". Get another?" ) ){
				next();
			}
		}
		else{
			alert( "Got friend "+ json.data[0].name + ". That's it!" );
		}
	}).error( function(){
		alert("Whoops!");
	});

Error handling

For hello.api([path], [callback]) the first parameter of callback upon error will be either boolean (false) or be an error object as described below.

Error Object

Extending the services

Services are added to HelloJS as "modules" for more information about creating your own modules and examples, go to Modules

OAuth Proxy

Services which rely on the OAuth 1 authentication method require a server side handshake with the secret key - this is unlike client-side OAuth 2 which doesn't need a secret and verifies the app based on the redirect_uri property.

Making HelloJS work with OAuth1 endpoints requires a proxy server to authorize the user and sign subsequent requests. As a shim HelloJS uses a service hosted at http://auth-server.herokuapp.com/ developers may add their own network registration AppID/client_id and secret to this service in order to easily get started.

The aforementioned service uses //node-oauth-shim, so go npm install oauth-shim that for your own deployment.

Browser Support

1. IE7: Makes beeping sounds whenever the POST, PUT or DELETE methods are used - because of the XD, IFrame+Form+hack.
2. IE7: Requires JSON.js and localStorage shims
3. Opera Mini: Supports inline consent only, i.e. reloads original page.
4. WP7: Supports inline consent only, i.e. reloads original page.

Contributing

"No, It's perfect!".... If you believe that then give it a star.

Having read this far you have already invested your time, why not contribute!?

HelloJS is constantly evolving, as are the services which it connects too. So if you think something could be said better, find something buggy or missing from either the code, documentation or demos then please put it in, no matter how trivial.

Changing code?

Please adopt the continuous integration tests.

	# Using NodeJS on your dev environment
	# cd into the project root and install dev dependencies 
	npm install -l

	# run continuous integration tests
	npm test

Open a couple of browsers with the given URL (e.g. it'll say "Karma v0.9.8 server started at http://localhost:9876/"). The tests are triggered when the code is modified