Milestone 1: user authentication 2. Create a table (USERS) for storing user information (see example 12.3 in Nixon's book). It should contain 2 fields per record, namely: userid and password. The password should be stored in encrypted form (after salting and hashing) (see example 12.4 in Nixon's book). 3. Implement the functionality that allows a user to login (by entering their userid and password and matching against the data stored in the USERS table in the database). See example 26.7 in Nixon's book for the basic functionality (ignore the visual aspects, please!). After successful login, display a page that shows a simple Success message. 4. Implement the functionality that allows a user to sign up (by entering their intended userid and password): if the userid is no longer available, display an error message; otherwise, add the new userid and associated (encrypted) password to the USERS table in the database and display a simple Success message. (Optionally, you might want to enforce password rules, such as minimum length, etc.) 5. Improve the visual aspects of your login/signup page and make it Bootstrap-based.

Modify your authentication process to implement the notion of a session. More explicitly, you should be able to create a session upon successful login and destroy the session after the user logs out (see examples 12.5 and 12.8 in Nixon's book). 8. Test your implementation of a session by conditioning the access to the wall page to successfully logged in users only. If a user is not logged in and tries to access the wall they should be redirected to the login page (see example 12.6 in Nixon's book). 9. IMPORTANT: NAMING CONVENTIONS o Name your main file (with login/signup screen) index.php o Name your wall file (which should only be accessible to registered users) wall.php o Make both files available at your p7 folder