Got a question about my Django development that I'd appreciate some sage "best practices" advice on.
My Django app needs more user capability than is available in the default middleware. Specificially I need to be able to: o "age" passwords; o do checks on validity of new passwords - make sure they're not reused, are greater than a minimum length and are "strong"; o lock out accounts after a certain number of failed attempts; o have a capability like the "roles" or "profiles" one - so user A needs to be able to just view data, user B needs to be able to acknowledge login warning messages and reset locked users, user C needs to have full access to user admin features, etc. I figure that the best way to do this is to use the sessions features in Django, but avoid the in-built user capability. I'm more than happy to generate all the screens and code that are needed, but I obviously don't want to do that if there's a simpler/better way. For obvious reasons I really don't want to end up patching/extending the Django code (and then have to redo my changes when Django 1.4 comes out). Thanks. Bob -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
