Added Closing Survey Feature, User Entity Feature, and Perform Authorization Checks Feature

[GillesMyny1]

This feature update includes the following:

• A User entity is now available, a User can be an ADMIN or STANDARD
• You must login at /index now as either an ADMIN or STANDARD
• Limited functionality has been put in place for STANDARD roles
• ADMIN roles can close Survey objects to view the results
• All appropriate tests for the User entity

[GillesMyny1]

Please discuss below about any comments or improvements that can be made.

[GillesMyny1]

This pull request covers the following issues #51 and #52

[dowy24]

Hi Gilles, good work on this new feature. How do I access the survey? Is there a default admin Username and Password or is there an option to create one?

[GillesMyny1]

Hi Gilles, good work on this new feature. How do I access the survey? Is there a default admin Username and Password or is there an option to create one?

Hey, thanks. As this is a software that is delivered to a client (the admin) and their users (the standard) there is currently functionality for an admin and standard users. Meaning that a client would setup both accounts, prepare the surveys, and send out the standard login info to their users.

The admin username and password are both "admin" for testing purposes.
The standard username and password are both "standard" for testing purposes.

[joshua-gatto]

How are the individual URLs protected from user input when they are not logged in, or do not have access to said functionality?

[GillesMyny1]

How are the individual URLs protected from user input when they are not logged in, or do not have access to said functionality?

Each URL get mapping has protections set in place to not only check if a session exists, where nobody is logged in, but also to check if the active session has admin or standard privileges.

Meaning that a user can only access URLs that their respective access rights allow.