OP-338 Preside data objects for storing the core website user data
OP-338 Refactoring the names of our data objects for front end user management
OP-338 Moving the website user management type data objects into their own folder
OP-338 beginnings of website user management service for handling login, security access, etc.
OP-338 implementing the getLoggedInUserDetails() method
OP-338 implementing the getLoggedInUserId() method
OP-338 implementing the logout() method
OP-338 Beginning to implement login method for website member service
OP-338 storing user data in session scope on login
OP-338 Refactoring website user data model to include a 'display_name' field. Figuring that is such a common requirement that it should be included in the core implementation
OP-338 Refactoring the login method for better readability and extensibility
OP-338 Moving and renaming service object to be more inline with current naming conventions
OP-338 Refactorig permissions config to separate out the concepts of front end website perms and admin perms
OP-338 creating a new cache for website context permission lookups
OP-338 adding a priority field to website benefits so that permissions granted through one benefit will overrule permissions granted on benefits with a lower priority
OP-338 refactoring so that we have a single 'applied permission' object for website user permissioning. This object can store direct user / benefit permissions as well as contextual permissioning
OP-338 Beginnings of website user peermissioning business logic
OP-338 Testing permission key filtering
OP-338 Making listing permission keys by user actually work
OP-338 refactoring private naming referencing the website user service (was using 'loginService' before)