uhm. Before smashing heads against the wall, there are 3 different "available methods" here.....
1) rely on nginx to authenticate users through pam (kinda of a basic auth, but checked against PAM) 2) rely on uwsgi to authenticate users through pam (kinda of a basic auth, but checked against PAM) 3) rely on web2py module to authenticate users through pam You want the users to reach web2py no matter what, and let the authentication happen using "web2py's logic".... assuming that the only thing you want is not having the username/password combos checked against a table in web2py's database but against PAM's database. Unless I understood it wrong, apache and rocket work. This means (if you didn't mess with apache configs) that 3) works "out of the box" What it seems by your config is that you're trying to do 2), i.e. stopping users "one step before", letting uwsgi interact deal pam authentication......that is a different thing. Do you want 1), 2) or 3) ? -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
