spatie/laravel-permission 没有名为 `edit_project` 的权限用于保护 `api`

Question

我正在使用带有 spatie/laravel-permission 版本 2.9 的 Laravel 5.6，还使用带有 $guard = 'api' 的 Laravel Passport 作为身份验证驱动程序。

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

public function assignPermissions($role, $permissions)
    {

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

        $role->givePermissionTo($permissions);

        return $role;
    }

但收到错误 There is no permission namededit_projectfor guardapi`。

我也有 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 是 web。

但我手动将guard_name 字段更改为“api”，我的权限表变成了这样。

Answer 1

从

移动 web 和 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

Answer 2

除非另有说明，否则包使用默认保护。否则指示它的方法是将以下内容添加到Role 类public $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' => Spatie\Permission\Models\Role::class, 更改为'role' => \App\Models\Role::class, 来在config/permissions.php 中注册您的Role（当然这会根据您的Role 班级所在的位置而有所不同）

您问题中的示例还提到了add_project，但数据库显示create_project，因此请确保您在所有地方都使用相同的名称。

Answer 3

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

Answer 4

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

php artisan cache:forget spatie.permission.cache 

然后

php artisan cache:clear

Answer 5

清除缓存php artisan cache:clear

如果这不起作用，请使用sudo php artisan cache:clear，一旦我使用 sudo，它就对我有用

Answer 6

清空数据库中的角色和权限表，然后重新填表。我有这个错误，我用这种方式修复了它

Answer 7

您需要在创建角色或权限失败时指定保护，其中 spatie 将承担出现在 config/auth 中的第一个保护，在这种情况下为“web”

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

您需要按如下方式处理：

// Create a manager role for users authenticating with the api guard:
$role = Role::create(['guard_name' => 'api', 'name' => 'manager']);

// Define a `edit_project` permission for the admin users belonging to the api guard
$permission = Permission::create(['guard_name' => 'api', 'name' => 'edit_project']);

Answer 8

这可能是权限问题。运行下面的命令。

sudo php artisan permission:cache-reset