JavaScript for Line of Business Applications

Using Favatron as a guide, I will take you through the entire process of creating a fully functional production ready Node web application. Some of the many parts we will touch on include authorization, user accounts, data storage, background workers, security, email, APIs, RSS, third party service integrations, and much more.

I am proud to introduce Twitatron, the web application we will be making. Twitatron will automatically monitor your Twitter account for mentions. When it finds those mentions, it will process them, store them, show them in the UI, expose them via an API endpoint and RSS feed, send an email digest, and share weekly stats with integrated social networks.

One way to implement authentication/authorization in single page Backbone application, with node.js/express on the server.

• Authentication in single page
• Login user
• Persistent login with cookies
• Sighnup
• Logout
• User roles - public, user, admin
• Determinig which routes are viewable based on the user's role

• Basic web forms

Our application will be split in two — a front-end web client written with EmberJS, and a JSON API powered by ExpressJS — each within their own self-contained project.

If you want to use JWT in your Ember Apps today there is a new extension by the team behind Blimp (Jose Padilla and Giovanni Colazzo) for the popular Simple Auth Add-on by Simple Labs.

The goal of this project is to learn how to build an authentication and authorization mecanism with AngularJS and a RESTful api running on a Node.js server. We can’t use cookies or sessions like an ordinary web application. So, we will use a token mecanism to authenticate our users.

When a user sends his credentials, the Node.js server checks that they are correct and answers with a unique token built with the user informations. The AngularJS application stores the token in the user’ SessionStorage and adds an Authorization header containing the token in every requests made after that. If the endpoint is restricted to authenticated users, the server checks the validity of the token and returns the data if the token is valid or a status code 401 otherwise. In addition to that, the AngularJS application checks if the user is logged in and if he can access the requested route. Otherwise, the user is redirected to the login page.