Authentication for user accounts
A service should be created to receive email and password for authentication. Service should accept an additional value flag which indicates whether or not to return a result that will redirect the user upon success or failure; or to return a simple string that can be utilized in AJAX requests to determine the next action.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Thomas Ingham
- Direction:
- Needs approval
- Assignee:
- Kai Blin
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Kai Blin
- Completed by
- Kai Blin
Related branches
Related bugs
Sprints
Whiteboard
Basic authentication works.
There's an auth controller that supports the following actions:
login - Displays a login form with email/password fields
submit - checks if the user exists and/or the password matches. When called with the "ajax" id, it will return the strings "no such user", "password mismatch" or "success", otherwise it'll redirect either back to the login action or the logged_in action.
logged_in - Displays a success message
logout - will log out the user. when called with the "ajax" id, it will return the string "logged out"
check - currently returns "Logged in as <email>" for logged in users and "not logged in" otherwise.
[kai.blin]
Sept. 20, 2008
Updated above description to reflect the controller now being named "auth". Marking "implemented" as discussed on IRC.
[\kai.blin]
Work Items
Dependency tree
* Blueprints in grey have been implemented.
