On 4/30/09, mdipierro <[email protected]> wrote: > auth.settings.block_registration=True > auth.settings.gmail_login=True > > or block them all > > auth.settings.block_registration=True > > auth.settings.gmail_login=False > > > Then block_registration==True people can still register but their > database field registration_key will contain "pending". Until this > field is pending, they cannot login nor retrieve password. Only the > administrator can replace "pending" with blank and restore access.
I think it would be: block_registration: don´t allow user registration. require_permition: don´t allow users to login by default (requires admin to “unlock“ that account). gmail_login: allow users to login with gmail account. Other feature I like: gmail_first: if True, verify user account in gmail and if it can´t auth there, try in db. If false, try to select a row in db where email is [email protected] and if can´t auth, try gmail. Really a generic approach can be used, something like that: auth.login_engines = ('gmail', db, 'ldap') So we can have various sources of user accounts and web2py can try all in one auth (if first fails, try second, tird...). -- Álvaro Justen Peta5 - Telecomunicações e Software Livre 21 3021-6001 / 9898-0141 http://www.peta5.com.br/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
