The Auth system is really designed to have one instance (and one auth_user table) per application. You best bet is probably to use a single user table and just add a "user_type" field indicating the type of user. If you need different profile fields for each type, you can include all the fields in the table and selectively set the readable/writable attributes of the fields depending on the type of user (you can also have separate linked tables for each user type). You'll need to do some customizing of the registration and profile actions to deal with the different groups.
Another option is to create a separate app to handle the registration and authentication of one of the groups and use CAS<http://web2py.com/books/default/chapter/29/09#Central-Authentication-Service> . Anthony On Sunday, June 9, 2013 10:48:54 PM UTC-4, shartha wrote: > > Hello. In a situation with two (or more) groups of users, for instance in > an application where companies post jobs, and job seekers search for jobs, > if I have two separate tables for companies and job seekers, how can I use > the authentication that is shipped with with web2py? Users sign up to the > website as either a job seeker, or a company, but I'd like to have one > input form for their login (The application needs to check against both > tables). > > Any help would be appreciated. > > Thanks. > -- --- 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.
