Completely built-in authentication, authorization, users, roles, RBAC, etc.

Hi,

It seems like Laravel 5 is getting closer to providing more auth-type functionality with auth generators, and that's great, but it still seems like a good amount of overhead to have to do to set up authentication and authorization in a new app.

I want to install a new Laravel app and have my user auth system completely coded and working, including RBAC (role-based access control), etc.

e.g. what i would like to see, is if i run this:

composer create-project laravel/laravel myNewApp -withRBAC -pass

mypassword

and I go to the home page, i see the 'hello' page, and there is a link there to a login page and I can go log-in as user 'admin' with password 'mypassword'. i can also logout, etc.

is this an off the wall idea? it's kind of like the Wordpress "5-minute install", but on a better/more-minimal/app-dev-centric framework.

my guess is that most people are not using authentication, so this functionality will not become part of laravel, in which case i'm wondering what could be the easiest way to allow all of those things out of the box from the earliest point possible with the fewest keystrokes possible.

to me like the most infrastructure-y part of any framework is the auth/auth system, followed by a Django-like admin panel, so, to me, setting those things up for a new app should be almost completely invisible to a developer, outside of the developer actually choosing which roles get to view/navigate to certain routes/pages/buttons/etc., pointing to a db, etc.

this is not a knock against Laravel or any other framework -- just curious if i'm the only one who really hates having to mess with auth code. :)

now i'm curious if any app framework provides auth out of the box (not including Wordrpess)...

andy

11 years ago

Level 8

I'm gonna go on the No side for this, because, where do you draw the line between framework and something like modx/drupal and such? At first I wasn't really thrilled that illuminate/HTML was dropped but after thinking of it it actually makes sense to pull it out of the core framework since it was doing just a little too much.

Doing too much and not doing enough is a fine line ...

More specifically, Authen/Author really depends on your needs.

I'm really mixed about the laravel starter app. It's just enough to give a novice a kick start but not enough to cover more advanced topics. But it does give you a pretty good head start for authentication for your app.

3 likes

jekinney

11 years ago

Level 47

I would like to see a first party package for auth with roles and permissions for Mr Tayler. I have developed my own with L4 because the other packages seem to either have way to much and cause overhead issues or hard for beginners to grasp.

2 likes

kfirba

11 years ago

Level 50

In my opinion, when it comes to such sensitive functionality, as the developer / site-owner I would like to rest assured knowing that I know what every piece of code does, how I can extend it and what functionality I have. I will feel more comfortable when I know that I'm the one who built it.

1 like

Please or to participate in this conversation.