A3M - Account Authentication & Authorization Module

[eluser]sirwan.me[/eluser]
Hi, there yeahs I wrote that article. I hope to help document A3M sufficiently enough and eventually create Video Tutorials on how to use it. I'm also willing to design the user interface of the administration area.

I think logging in with the username is by far the best option.. a username is an online identity, and peoples email change. usernames make the identity on a website for less complex. a username can be used for everything all at once... ie.

- login in
- comment
- post
- avatar
- Profile field. e.g. http://domain.com/USERNAME

i firmly stand by only logging in via username. I dont see why not. Besides, with A3M people authenticate via gmail, facebook etc.... SO What if he/she loses 'email' if they use a social networking site to login in.

For me, this is my strongest opinion on the entire features of a auth lib.

final points-

- easier to program the flow of the entire app with usernames.
- one id, is better than an email AND a username
- Clearer programming when linking usernames to other things like Profile, Posts, comments, etc
- Lost password should not be an issue, just have an auto generated password.
- Account verification is redundant, ... If the user hasnt logged in after 4 days of signing up.. clean him/her away.


Im of the philosphy... of SPEED, SIMPLICITY (both for developers, designers and end users.)

Lets not make this a sudoku puzzle. and just give the end users what they want simple.

thanks
ill be blogging about this on sirwan.me