how to use single login page for users in four models

how to use single login page for users in four models

ram kris wrote in post #1114502:

how to use single login page for users in four models

You have not given enough detail in your question to know what you're
asking.

Are you saying that you have four different types of users? If so then
why do you have four models instead of doing role based authorization
having only one user model?

If you really do have four different types of user then you might want
to consider Single-Table-Inheritance (STI). I seriously doubt you need
to go to this extreme though.

I can't give you a definitive answer from such an abstract question.
There are many ways to solve a problem, but you haven't even described
the problem you're trying to solve.

Robert Walker wrote in post #1114535:

ram kris wrote in post #1114502:

how to use single login page for users in four models

You have not given enough detail in your question to know what you're
asking.

Are you saying that you have four different types of users? If so then
why do you have four models instead of doing role based authorization
having only one user model?

If you really do have four different types of user then you might want
to consider Single-Table-Inheritance (STI). I seriously doubt you need
to go to this extreme though.

I can't give you a definitive answer from such an abstract question.
There are many ways to solve a problem, but you haven't even described
the problem you're trying to solve.

@Robert Walker plz clarify me

i have face the same problem.i have two models employee(having 6 input
fields),client(having 12 input fields),i need to authenticate them using
devise.what i have to do single sign in form for both if it is solution
let me know how is this,else by using two devises or any solution let me
know

thankyou @Robert Walker

Robert Walker wrote in post #1114535:

ram kris wrote in post #1114502:

how to use single login page for users in four models

You have not given enough detail in your question to know what you're
asking.

Are you saying that you have four different types of users? If so then
why do you have four models instead of doing role based authorization
having only one user model?

If you really do have four different types of user then you might want
to consider Single-Table-Inheritance (STI). I seriously doubt you need
to go to this extreme though.

I can't give you a definitive answer from such an abstract question.
There are many ways to solve a problem, but you haven't even described
the problem you're trying to solve.

@Robert Walker plz clarify me

i have face the same problem.i have two models employee(having 6 input
fields),client(having 12 input fields),i need to authenticate them using
devise.what i have to do single sign in form for both if it is solution
let me know how is this,else by using two devises or any solution let me
know

thankyou @Robert Walker

Robert Walker wrote in post #1114535:

ram kris wrote in post #1114502:

how to use single login page for users in four models

You have not given enough detail in your question to know what you're
asking.

Are you saying that you have four different types of users? If so then
why do you have four models instead of doing role based authorization
having only one user model?

If you really do have four different types of user then you might want
to consider Single-Table-Inheritance (STI). I seriously doubt you need
to go to this extreme though.

I can't give you a definitive answer from such an abstract question.
There are many ways to solve a problem, but you haven't even described
the problem you're trying to solve.

@Robert Walker plz clarify me

i have face the same problem.i have two models employee(having 6 input
fields),client(having 12 input fields),i need to authenticate them using
devise.what i have to do single sign in form for both if it is solution
let me know how is this,else by using two devises or any solution let me
know

thankyou @Robert Walker

The simplest thing of all would be to have a single "User" model and a has_one sidecar model for the Client's extra fields. That way you can have just one set of login / logout paths and not worry about the logged-in person's underlying class. Using CanCan to manage the authorizations, you can allow an employee to see or do things that a client cannot, and vice-versa. Storing the "what kind of user this is" attribute in a column and switching permissions on that value is one of the simplest things to do in a multi-role application using CanCan. I recommend a quick read of the Wiki on that GitHub project.

Walter

This is probably me just being crazy, but why have so many devise tables? You may indeed have different user types, but if they all need to log in, then why not have a single User table that handles the authentication that is common to all types? Do you really need different methods of logging your various types of users in? You can either then have different models for the 4 types, but they can all either inherit from User (which is the single table inheritance thing) -or- they can be separate models with their own relationships and such to the User table you use for authentication.

If you really want to think about it, you don't need to make this part of you application at all, and use Devise as a completely separate Rails Engine with it's own models. All your application needs to deal with is authenticated users, and none of the business of actually authenticating them.

@ Walter Davis thankyou
can you give me the sample code or any link.I did not get any resource
plz let me know.
Thank you

@ Walter Davis thankyou
can you give me the sample code or any link.I did not get any resource
plz let me know.
Thank you

Here. Watch some movies. http://railscasts.com/episodes?utf8=✓&search=cancan

Walter