[eluser]Peng Kong[/eluser]
[quote author="taziz" date="1285114783"]I've been modifying a3m for a project I'm working on and it seems like my changes are what others here are looking for. Once I finish my project I'll try and start a fork for anyone who is interested
Changes in my code include
1) Removed username, log in is done with email
2) Email verification added in
3) Updated facebook/twitter to latest api version
4) When signing on initially with a third party system I ask the user to enter their email and choose a password so they can log in to the site nativity in the future. No verification email is sent out in this case as that is a bit redundant.
5) Welcome email sent out when email is verified or third party account log in process is completed.
TODO
1) Figure out the oauth system to support authentication for an API
2) Ban users/Delete users
3) Fix profile pages
4) Admin UI
I know this method goes against the simple log in model this project aims for but it's what I need for my current project. Again if anyone is interested I will share my code once completed[/quote]
very cool! a3m was intented for this purpose. easily modifiable to suit your specific need. easily upgradable to keep up with changes in third party packages.
btw i also hack my own a3m for my company just today.
one a3m serves as a single sign in point for many sites sitting in different subdomains.
each site will redirect the user to a3m to sign in. once signed in a3m will redirect the user back to the correct website. and depending on which site the user came from, a3m will adopt a different css skin it was quite a heavy hack, but it's working sweet.