Dear web2py' ers,
Can anyone point me to some guidance or best practice on how to do
user management, self-registration, authentication and authorization
in web2py?
I am currently struggling with a Django project where I have spent
upwards of 50% of my learning curve on these issues and before leaping
fully into web2py I'd like to make sure that I don't wind up in the
same situation.
Ideally I'm looking for the following:
1. A way to securely tie an authenticated user to a web2py session
object; (without using CAS, see below)
2. A self-registration/activation flow by e-mail that I can tightly
integrate with my app (unlike CAS).
3. A way to group users;
4. A way to limit access to application objects, not just at the
function level ("a/c/f") but also at the data/row ("?id=x");
I have looked at CAS but apart from not being able to get it to work
(what is my_url...? what is the flow of redirections?) it is too bare-
bones and "stand-alone" for my app (eg, email+password only...) -- so
I'd have to patch the CAS server as well, and that feels like a repeat
of my Django experiences (django-registration, brrrr). "T2" sounds
promising but seems to be a work-in-progress at the moment.
If anyone here have example code or advice, I'd be very grateful.
Cheers,
-Peter
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
