-
Notifications
You must be signed in to change notification settings - Fork 2
Auth
The AuthController is responsible for control during an authenticated (user logged in) session.
- logout: End the session
- updateuserInfo: Update the user's information
- checkNewUsername: Check for username availability. I worked ona project that had a business requirement: "The user can change their user id." or something to that effect. I thought it was the dumbest thing I ever heard. Then I was on a site and realized my email was my username and that can change, so why would I want to sign up for a new account? Put it in. One downside (to the user) is if they change their ID (username) they have to reset their password since the backend server uses username as part of the password hash
- checkNewEmail: Users can also change their email address. But this also has to be unique in this system. So this checks for email availability. Potential confusion may arise if the user changes their email but doesn't validate it. Might need to add a system notification on login.
#../
\enyo-mvc-web-app
|
+---index html
+---mvcApp html
+---mvcAppDebug html
+---package json
+---node-server js
+---mvcApp html
+---assets
+---enyo
+---lib
+---node_modules
+---public
+---scripts
|
\---source
|
+---apps
+---controllers
| |
| +---auth
| \---public
|
+---css
+---ext
+---models
| |
| +---ajax
| \---socket
|
\---views
|
+---auth
| |
| \---body
|
\---public
|
\---body
Add a Contact Page for Authorized users
Why is the project structured this way?
Why are some things implemented this way?