Authentication

[daveharmswebdev]

User Story

As a user I want to be able to login and logout so I can protect my data.

Acceptance Criteria

• User logs in with email and password.
• Password requires at least 8 characters, at least one numeric, one upper case letter, and one special character, and no consecutive letters.
• Username is an email of valid email form.
• If a user is not logged in, user will be shown a log in screen.
• A link to register will be on the log in screen.
• Users not registered or not logged in will only have access to registration, about and contact.

[daveharmswebdev]

We need the ability to create an account. Then we need the ability to login and logout. And when you are logged in the application should state explicitly who is logged in. At the very least have the name in the upper right corner, displayed at all times, therefore fixed.

A stretch goal would be to have a photo (thumbnail) applied next to the name.

This means we need to have the ability to edit a profile.

• Last name
• First name
• Middle Initial
• Birthdate -> age
• Phone number -> this will be used for sms notifications
• email -> also used for notifications and to send reports
• address, city, zip, state (useful for when transmitting data to providers, for proper patient identification)

stretch goals

• a way to upload photos

[daveharmswebdev]

Doc Apr 02, 2017, 14:39.pdf

This is the log in page, simple user and pass to log in. There is a simple link if not a member, which leads to register page.

route: /account/login

[daveharmswebdev]

Doc Apr 02, 2017, 14:45.pdf

This is the register view, when pressing continue, takes you to profile view, profile will be required to complete registration, it is not something that can be skipped, done later.

route: /account/register

[daveharmswebdev]

profile.pdf

Registration is complete with completing the profile page, of course there is a button

route: /account/profile

[daveharmswebdev]

stretch goals: forget/reset password. Validate email.

[daveharmswebdev]