I've decide to use multi authentication for laravel 5.1 in a project for basic reasons. But i'm facing a problem with @can blade directive. Virtually, this directive returns true to anything, which did not precede before using the basic auth native from Laravel 5.1. The user has a Role relationship which returns a collections of Permissions contains the following attributes:
id;
name;
label;
the label attribute is the string with the permission name in snaked case.
I can not resolve this using a new implementation for check permissions because i'm talking about a project in advanced production stage. I hope it's a problem with how i implemented the Multi Auth, maybe i miss something on tutorial... could you help me?
Hi, Sarav.
I've decide to use multi authentication for laravel 5.1 in a project for basic reasons. But i'm facing a problem with @can blade directive. Virtually, this directive returns true to anything, which did not precede before using the basic auth native from Laravel 5.1. The user has a Role relationship which returns a collections of Permissions contains the following attributes:
the label attribute is the string with the permission name in snaked case.
I can not resolve this using a new implementation for check permissions because i'm talking about a project in advanced production stage. I hope it's a problem with how i implemented the Multi Auth, maybe i miss something on tutorial... could you help me?