Added permission_codes method to User for getting an array of permission codes associated to a given user for each role they have
Added method on ApplicationController called can? that can be used to validate the current_user has a given permission
Added method_missing to ApplicationController so extending controllers can define before_filters in the format of 'authorize_somepermissioncode' to authenticate controller methods against permissions the current_user should have at the time
Removed the NOT NULL from users employee_id and updated the user spec around creating root and admin users to ensure the generated users are valid
Added an allow_nil to the employee_id attribute on user and upated the spec.  Also well I added a save! to the create customer service and removed the mocking of save from the spec
Added access denied method to ApplicationController and skeleton errors layout and access_denieded error page to be used on conjunction with can?
Updated ApplicationController.method_missing to call access_denied! if the current_user does not have a given permission
Updated errors layout to yeild the content of the views using it
Fix an issue where there was in inconsistency when it came to the Permission roles gotten by user.permission_code that where Strings and the can? method check in ApplicationController that was using Symbol types.
Reverted the constant Permission::Code to be a string value instead of a symbol, this is an ok approach for now until I find a better strategy for constants using symbols and the conversions of them to sym from the database.  Rails 4.1 enums are an interesting option but I don't like storing those values as integers
Updated can? method in ApplicationController to allow for the use of permission or role codes to do authorization checks
Updated controllers to include permission and/or role based authorization checks as well as made the access denied page look a little better
Removed the ability to use the can? method with roles, instead it is now fully permission based and if the view or controller needs to check multiple permissions then it should do so by stringing together multiple permission checks so the view is completed abstracted away from roles
Merge pull request #26 from lenzenc/ISSUE#24

Merge ISSUE#24 - Add Authentication