spatie / laravel-permission对于警卫`api`没有名为`edit_project`的权限

时间:2018-03-03 17:19:45

标签: php laravel laravel-5 spatie

我正在使用Laravel 5.6和spatie / laravel-permission 2.9版,同时使用Laravel Passport作为$guard = 'api'的auth驱动程序。

当我尝试借助此功能将['edit_project', 'add_project' 'delete_project']等权限数组分配给角色时

public function assignPermissions($role, $permissions)
    {

        $role = Role::findByName($role);

        $role->givePermissionTo($permissions);

        return $role;
    }

但收到错误There is no permission named edit_project for guard api`。

我也有config / auth.php

return [

/*
|--------------------------------------------------------------------------
| Authentication Defaults
|--------------------------------------------------------------------------
|
| This option controls the default authentication "guard" and password
| reset options for your application. You may change these defaults
| as required, but they're a perfect start for most applications.
|
*/

'defaults' => [
    'guard' => 'web',
    'passwords' => 'users',
],

/*
|--------------------------------------------------------------------------
| Authentication Guards
|--------------------------------------------------------------------------
|
| Next, you may define every authentication guard for your application.
| Of course, a great default configuration has been defined for you
| here which uses session storage and the Eloquent user provider.
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data.
|
| Supported: "session", "token"
|
*/

'guards' => [
    'web' => [
        'driver' => 'session',
        'provider' => 'users',
    ],

    'api' => [
        'driver' => 'passport',
        'provider' => 'users',
    ],
],

/*
|--------------------------------------------------------------------------
| User Providers
|--------------------------------------------------------------------------
|
| All authentication drivers have a user provider. This defines how the
| users are actually retrieved out of your database or other storage
| mechanisms used by this application to persist your user's data.
|
| If you have multiple user tables or models you may configure multiple
| sources which represent each model / table. These sources may then
| be assigned to any extra authentication guards you have defined.
|
| Supported: "database", "eloquent"
|
*/

'providers' => [
    'users' => [
        'driver' => 'eloquent',
        'model' => App\User::class,
    ],

    // 'users' => [
    //     'driver' => 'database',
    //     'table' => 'users',
    // ],
],

/*
|--------------------------------------------------------------------------
| Resetting Passwords
|--------------------------------------------------------------------------
|
| You may specify multiple password reset configurations if you have more
| than one user table or model in the application and you want to have
| separate password reset settings based on the specific user types.
|
| The expire time is the number of minutes that the reset token should be
| considered valid. This security feature keeps tokens short-lived so
| they have less time to be guessed. You may change this as needed.
|
*/

'passwords' => [
    'users' => [
        'provider' => 'users',
        'table' => 'password_resets',
        'expire' => 60,
    ],
],

];

如果有任何解决方案,请帮助我,谢谢。

我也是在Larvel播种机的帮助下播种了权限表,我的权限表第一次看到了guard_name就是这样。

enter image description here

但我手动将guard_name字段更改为“api”,我的权限表就像这样。

enter image description here

6 个答案:

答案 0 :(得分:1)

移动网页和api位置
'guards' => [
    'web' => [
        'driver' => 'session',
        'provider' => 'users',
    ],

    'api' => [
        'driver' => 'passport',
        'provider' => 'users',
    ],
],

'guards' => [

        'api' => [
            'driver' => 'passport',
            'provider' => 'users',
        ],

        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
    ]

运行php artisan cache:clear

答案 1 :(得分:1)

创建权限后,运行以下命令应该对我有用。

php artisan cache:forget spatie.permission.cache 

then 

php artisan cache:clear

答案 2 :(得分:1)

清除缓存php artisan cache:clear

如果这不起作用,请使用sudo php artisan cache:clear,它在我使用sudo后对我有效

答案 3 :(得分:0)

除非另有说明,否则包使用默认保护。另外指示它的方法是将以下内容添加到Rolepublic $guard_name = 'api';。当然,将它添加到vendor目录中的类是一个坏主意,所以你想要扩展它并指定像这样的守卫

use Spatie\Permission\Models\Role as OriginalRole;

class Role extends OriginalRole
{
    public $guard_name = 'api';
}

如果您还没有这样做,请使用php artisan vendor:publish --provider="Spatie\Permission\PermissionServiceProvider" --tag="config"生成配置文件

最后,您希望通过将Role更改为config/permissions.php'role' => Spatie\Permission\Models\Role::class,注册'role' => \App\Models\Role::class,(当然,这会因您的{{1}而异} class is)

此外,您问题中的示例提及Role,但数据库显示add_project,因此请确保您在所有地方使用相同的名称。

答案 4 :(得分:0)

在您的用户模型中添加protected $guard_name = 'api';,这将覆盖默认的保护范围,即 web

答案 5 :(得分:0)

清空数据库中的角色和权限表,然后重新填表。我遇到了这个错误,我是这样修复的