Multiple User Authentication System

I would have thought it would be more like:

• Admin (domain.com/admin)
• Brands (domain.com/brand)
• Users (domain.com/user)

But all are users. Also look here and at other links in there. https://laracasts.com/discuss/channels/general-discussion/authorization-policies-and-reducing-the-repitition

and

https://laracasts.com/discuss/channels/laravel/security-in-controller

Usually a good RBAC with correct queries does the job.

For what you want also look at: https://github.com/spatie/laravel-permission

you're wasting your time, you have to use roles and permissions.

roles: admin, brands, users permissions: administrator, brand, user, guest.

you don't need separate your authentication in 3 types. that would be very dirt.

if all user types are accessing the same resources or related, i would suggest to use singler url and control the access with the user, user group, user role and permission.

@siangboon could you please explain what you mean by a Singler URL ?

@lightyagami Could you please share an example of how I can implement the same?

Hi @harshamv, in this repo I do it and commit it. larasin. See this commit: Manage Multiple Authentication.

admin.domain.com, brand.domain.com, users.domain.com are 3 different URL, usually people use different url for different projects or purposes. What i meant single url is all 3 types of users are accessing at the same login url and use the role and permission to control their access of the view and actions on to the resources accordingly.

to implement role/permission, you can refer the lessons here: https://laracasts.com/series/whats-new-in-laravel-5-1/episodes/13 https://laracasts.com/series/whats-new-in-laravel-5-1/episodes/14 https://laracasts.com/series/whats-new-in-laravel-5-1/episodes/15 https://laracasts.com/series/whats-new-in-laravel-5-1/episodes/16

@hakhsin thanks a lot will check it out. Is it your repository? If I have any questions can I ask here?

@siangboon thanks a lot. went through them. It is clear. In my app we will have three sub-domains itself but render the app from single source code. We have been doing the same in Rails for the last three years.

Just moving to Laravel so figuring out how to build on laravel.

I see.

Perhaps this video may help you: https://youtu.be/iKRLrJXNN4M?t=915

@siangboon yes was checking this out. Thanks a lot. Hope I can get this to work somehow and move on to the fun part.

Hi @harshamv. Yes, it's my repo. Yes, ask me here.

Another good permission repo is from spatie https://github.com/spatie/laravel-permission They create a lot of laravel packages which are great!

Of course I mentioned https://github.com/spatie/laravel-permission earlier. But why can't you use the same style RBAC you used in Rails here. Nothing prevents you from using custom authentication and authorization (RBAC).

I also use cake and yii for projects thus stay away from some framework biased code. I like RBAC that can work in any language with small tweaks.