Ok, thanks. So I have an idea involving groups. I edited my auth_user
table, I did that with no problem but I cant seem to link it to
another table so I get a drop down in one of the fields:
Here is my model (notice IS_IN_DB):
##Aditional table to support auth_user
db.define_table('department',
Field('name'),
Field('abbreviation'),
Field('committee'))
##Additional auth_user fields
auth.settings.extra_fields['auth_user']= [Field('company'),
Field('department',db.department)]
db.auth_user.department.requires=IS_IN_DB(db,'department.id','%
(name)s')
The error, cant find auth_user.
Thanks
On Feb 28, 5:40 pm, Massimo Di Pierro <[email protected]>
wrote:
> You can have two auth objects and you can swicth between them using
> for example a session variable or a parameter in the URL. Yet is is
> going to be a mess.
>
> I suggest instead you use one auth table and user roles and
> permissions to decide who can do what.
>
> massimo
>
> On Feb 28, 4:12 pm, greenpoise <[email protected]> wrote:
>
>
>
>
>
>
>
> > Sorry, I pressed enter without being finished:
>
> > My second option
>
> > 2. Build a table called employee that uses only one auth table.
>
> > Either way I am stuck on how to do this.. First would like to know
> > which is a good practice and second, how could I accomplish this??
>
> > Thanks
>
> > dan
>
> > On Feb 28, 2:10 pm, greenpoise <[email protected]> wrote:
>
> > > I have been searching in this group for a way of implementing two
> > > authentication within one application. My idea is to have Auth table
> > > managed by an administrator. However, I want to give the flexibility
> > > to added users to add their own employees and the employees being able
> > > to log into the application. My question is, is this a good practice?
> > > would it work??
>
> > > I can think of two options:
>
> > > 1. Having a second auth table and login process separate from the main
> > > auth table
