web2py definitely needs the auth tables to work with any auth backend (even LDAP). Of course username and pwd are stored in AD, but AD doesn't have, e.g, the user id. web2py uses auth_* tables for dealing with RBAC, and even if you don't need granular permissions, groups etc, it still has to map a user to a unique integer(ish) id. Moreover, auth_* tables assure you that you won't continuously hit the auth backend once authenticated (sort of a "cached" copy of what is needed is written into the database).
You shouldn't have problems with firebird .... what is the exception your app raises when trying to create the auth tables ? -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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.
