thinkjones/meanterprise

MEAN based single page application with common SPA enterprise application add-ons.

Meanterprise

This is a MEAN style application that builds off the typical Hello World seed templates by including common functionality present in many typical Enterprise applications.

• M - MongoDB
• E - ExpressJS - Server side application framework
• A - AngularJS - Client side application framework
• N - Node - Package manager

Additional Features:

• Server Side Authentication with PassportJS
• Client Side Route Security (Logical Security not Real Security)

Future Features:

• Nested routing
• Tidy CRUD Examples
• Python and Java backends

Setup

Install Node and Npm

brew install node

Install and Setup Mongo

brew install mongodb

Install dependencies

npm install

bower install

Start the application

Start Mongo

mkdir /tmp/mongo
mongod --dbpath /tmp/mongo

Start Application

npm start

Navigate to home screen: http://localhost:3000

Enterprise App Features

Server Authentication Security

Implemented using PassportJS using only the passport-google authentication strategy at present.

Client Route Security

Client Side Security (CSS) is managed using a pattern inspired by the angular-client-side-auth repository. The short description of the CSA pattern is:

1. Add access role to your routes:

 $routeProvider.when('/',
        {
            templateUrl:    'home',
            controller:     'HomeCtrl',
            access:         access.user
        });

2. Create a security service

3. Check security of routes as they are about to change (app.js):

angular.module('app').run(['$rootScope','$location','security', function($rootScope, $location, security) {
    // Get the current user when the application starts
    // (in case they are still logged in from a previous session)
    security.requestCurrentUser();

    $rootScope.$on("$routeChangeStart", function (event, next, current) {
        if (!security.authorize(next.access)) {
            $location.path('/');
        }
    });

}]);

Future Enterprise App Features

• Server Endpoint Security
• Python and Java backends

Testing

Unit and e2e Tests Example unit and e2e tests are added to the project. These illustrate how automatic testing can be incorporated into the default grunt default workflow. Simply run the project and any time a source or test file changes the tests will be re-run.

Continuous Integration CI

---

There is a .travis.yml file for CI at Travis-CI.com

License

The MIT License (MIT)

Copyright (c) 2013 Gene Conroy-Jones

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

meanterprise's Issues

Server Request Security

I've been reading through http://www.frederiknakstad.com/2013/08/04/authentication-in-single-page-applications-with-angular-js-part-2/ and I'm wondering what it is about this approach to securing the server side that you didn't like? Is there any reason why I shouldn't implement this into your seed for my own use?