Make a server-to-server call using the token to check its validity.

There's more comments on this subject here https://github.com/MrSwitch/hello.js/issues/22

Point and space taken. Now it is readable - and I rather dread the consequences.

@ishi take a look at this example http://adodson.com/hello.js/demos/friends.html

Yes, but its a pretty arduous task digesting and implementing API docs. That pain was the impetus to standardize them into the HelloJS library.

PassportJS = NodeJS authentication, designed for single sign-on.

HelloJS = Browser + Phonegap authentication and API request handling designed to interact with thirdparty services from the client app.

Firebase simple login does provide similar functionalities right ?

Thanks for sharing my project HelloJS

Hi, thanks for putting this together and releasing it. I'd like to use it on our corporate intranet, but we use the OAuth2 implicit flow with JSON web tokens. Does hello.js support this use case?

I couldn't find any examples of JSON Web Token in the client. But if the security model supports it then i'd like to entertain the idea.

Hi... thanks for writing this. As a newb on these sorts of issues, I have some questions:

1. So this is 100% client side... Why do I see "npm" in the instructions? Isn't that connected to nodejs? What if I'm writing a java web server app, will this still work, or does it need to talk to a nodejs server somehow?

2. I take it none of this hits a third party server (i.e. your server)?

3. How do I get the user's info obtained via authentication (gmail address, etc) to my server, in a way that is secure, if this is all client & browser based?

1. NPM is just an easy way to install it, you can also use bower or just download the source and minified packages.

2. I see no reason why it would.

3. It's all client based regardless of how you do it, it just adds cookies. If you want to get the information server side just get it server side (PHP example https://github.com/thephpleague/oauth2-client) there is no need to get it client side if you need it server side with a server side library (thus why NPM is shown as node is server side).

Use node for bundling+minification.

Its on npm for convenience. I also hope to make it compatible with CommonJs and have components of it work through the server.

Not all services support server-less authentication otherwise known as Implicit OAuth2. As such, i've put a proxy service up on Heroku. Read up at http://adodson.com/hello.js/#oauth-proxy

1. NPM is used for installing bower [1], a package manager for client side libraries.

[1] http://bower.io/