JavaScript for Line of Business Applications

Authentication is one of the big parts of every application. Security is always something that is changing and evolving.

We’ll build a quick API using Node and Express and we’ll be using POSTman to test it.

The main workflow of this is that we will:

1. Have unprotected and protected routes
2. A user will authenticate by passing in a name and a password and get back a token
3. The user will store this token on their client-side and send it for every request
4. We will validate this token, and if all is good, pass back information in JSON format

Google’s OAuth documentation seems to indicate OAuth 2.0 for installed applications fits the bill for a mobile application.

The idea is to use an embedded web browser to show the OAuth consent page. If the user grants access, we can get the authorization code out of the embedded browser’s title property. We PhoneGap developers have InAppBrowser for embedded browsing, so this should be a piece of cake!

Ember.js's built in objects and structure are great, to use them correctly is to enjoy all it's power. So you wonder, what is the best way to use Ember.js's and it's well grounded structure to build your user's authentication?

This article will not cover the authentication api part, because it's already well covered on good articles like codeberry's Authentication With EmberJS - Part 1, which we will use in this example, but we'll use the rails gem instead of the rails-api gem to make use of the assets pipeline.

The part two on that article deals with the authentication task through EmberJS with an AuthManager component, which is clever idea, but it follows a path that leads to deal with the authentication part as a component, which leads to step outside of the framework's path in some cases, like accessing the store object outside of a route or controller. And it can lead to some problems or difficulties in the future.

In this article we show some nice features of Spring Security, Spring Boot and Angular JS working together to provide a pleasant and secure user experience. It should be accessible to beginners with Spring and Angular JS, but there also is plenty of detail that will be of use to experts in either. This is actually the first in a series of articles on Spring Security and Angular JS, with new features exposed in each one successively. We’ll improve on the application in the second and subsequent installments, but the main changes after this are architectural rather than functional.

In this post, we will take a look at the Integration between Firebase Simple Authentication and node-webkit. We are going to use slush generators to scaffold basic apps for us. Then we will create and configure a Firebase account to manage Simple Authentication i.e. Email and Password and Social Authentication using Twitter, Google and Facebook services.

However, once you start creating a bigger app, you realize that just using React isn’t enough. So you start looking at Flux, which is the architecture Facebook uses to create React apps.

As we learned in a previous blog post, learning how to conduct authentication in a Single Page App can get super complex. We had to learn about tokens, JWTs and how to integrate them with SPAs. Learning how to do it with Flux is even harder! That’s why in this blogpost we’ll learn how to add authentication to a React Flux app.

Token based authentication is prominent everywhere on the web nowadays. With most every web company using an API, tokens are the best way to handle authentication for multiple users.

The traditional way of having our applications remember who we are is to store the user logged in information on the server. This can be done in a few different ways on the session, usually in memory or stored on the disk.