Laravel 5.3 gurus, please help me as am new to Laravel framework.
Now I have a system am building, the system has 4 different types of users e.g

*Student Login

*Lecturer Login

*Admin Login

*Counsellor Login

each of them has their different tables in the database.

Laravel comes with just a single user authentication using the users table.

please how can I go about this ?
Thanks in advance!

You should not create different tables for similar contents. You can just have 1 user table and have a type column, that will specify the type of user.

However I think it's possible that a lecturer can also be an admin, the lecturer shouldn't have to logout first before he can now login as admin.

You can have a separate roles table, and a user_role pivot table to assign multiple roles to a user. This package does everything seemlessly https://github.com/Zizaco/entrust

This is a role privilege concept solution. Lecturer, students, counselor, and Admin are all roles so you have a table for keeping roles, and another table for keeping all users. Users belongs to a role and a role can have many users too; this concept means your application will be scalable and flexible enough for your users to add more roles in the future without writing any code if done properly

jidez007:
You should not create different tables for similar contents. You can just have 1 user table and have a type column, that will specify the type of user.

However I think it's possible that a lecturer can also be an admin, the lecturer shouldn't have to logout first before he can now login as admin.

You can have a separate roles table, and a user_role pivot table to assign multiple roles to a user. This package does everything seemlessly https://github.com/Zizaco/entrust

Thanks, I've used that method, I just use student, lecturer, admin as example. The app am working on is something far different and is a requirement that each entity has its table

talk2hb1:
This is a role privilege concept solution. Lecturer, students, counselor, and Admin are all roles so you have a table for keeping roles, and another table for keeping all users. Users belongs to a role and a role can have many users too; this concept means your application will be scalable and flexible enough for your users to add more roles in the future without writing any code if done properly

Thanks but the database has been built and populated already, the system was built on raw php before, I just wanna use laravel to add new features to it.

You should implement a guard so you can authenticate from each guard. Like this.

$validate->only($request['username'], $request['password'];

Auth::guard('table-name')->attempt ($validate){
//Authenticates.
}

But the ugly part with this method is that you have to do the ugly checking of not allowing specific user to gain access to another users routes or view.

Hope it helps any problem feel free to ask.

mohemos:

Thanks but the database has been built and populated already, the system was built on raw php before, I just wanna use laravel to add new features to it.

You can always transfer if you want to, all you need to do is write a simple script that will automate that for you

FrankLampard:
You should implement a guard so you can authenticate from each guard. Like this.

$validate->only($request['username'], $request['password'];

Auth::guard('table-name' )->attempt ($validate){
//Authenticates.
}

But the ugly part with this method is that you have to do the ugly checking of not allowing specific user to gain access to another users routes or view.

Hope it helps any problem feel free to ask.

Guards aren't table names. Are they?

Jregz:

Guards aren't table names. Are they?

It is not a must you name your guard equivalent to your table name. I only do it for the sack of remembrance.

talk2hb1:

You can always transfer if you want to, all you need to do is write a simple script that will automate that for you

Pls how I want to learn.

FrankLampard:


It is not a must you name your guard equivalent to your table name. I only do it for the sack of remembrance.

Ok... I thought you took guards as tables

You'll have to define a guard and a driver (in your case, probably session) and an eloquent user model for it. Then you can call Auth::guard('guard')->attempt().

If using session driver, your users table must have a username and password column. If using token driver, it must have an api_token column.

Hello, unfortunately I don't have a link i gave out to someone on how you can implement this.

if you don't probably mind, you can reach me just so I give you a link that solves this problem of yours tomorrow.

Best Regards.

mohemos:
Laravel 5.3 gurus, please help me as am new to Laravel framework.
Now I have a system am building, the system has 4 different types of users e.g

*Student Login

*Lecturer Login

*Admin Login

*Counsellor Login

each of them has their different tables in the database.

Laravel comes with just a single user authentication using the users table.

please how can I go about this ?
Thanks in advance!

Hi, i think if your users are having different tables, its a poor design.
Cos you'll most likely have two users with same identifier at some point unless you're doing some ugly checks.
This should have been accomplished using Eloquent relationships instead.
I don't know what you're trying to avoid, maybe you want to collect different types of data from the different types of users.
for example; you may want to store "job title" for lecturers and "department" for students. In this case you can have additional tables like "lecturers_data" and have it linked with lecturers, and another like "students_data" like that, such that you can fetch data from them using their foreign keys.

I think this is a better approach. Every other thing you need can be done with middlewares.
Goodluck!