dotkernel/dot-rbac-guard
Composer 安装命令:
composer require dotkernel/dot-rbac-guard
包简介
Dotkernel RBAC guards component
README 文档
README
Defines authorization guards that authorize users to access certain parts of an application based on various criteria. If the authorization service can be used to check authorization on a narrow level, the guards are meant to work as gateways to bigger parts of an application. Usually, you'll want to use both methods in an application for increased security.
Documentation
Documentation is available at: https://docs.dotkernel.org/dot-rbac-guard/v3/overview/.
Badges
Installation
Run the following command in your project's root directory
$ composer require dotkernel/dot-rbac-guard
Please note that this module is built around the authorization service defined in module dot-rbac. Running the above command will also install that package. You'll have to first configure dot-rbac before using this module.
Configuration
As with many Dotkernel modules, we focus on the configuration-based approach of customizing the module for your needs.
After installing, merge the module's ConfigProvider with your application's config to make sure required dependencies and default module configuration are registered.
Create a configuration file for this module in your 'config/autoload' folder.
authorization-guards.global.php
return [ 'dot_authorization' => [ //define how it will treat non-matching guard rules, allow all by default 'protection_policy' => \Dot\Rbac\Guard\GuardInterface::POLICY_ALLOW, 'event_listeners' => [ [ 'type' => 'class or service name of the listener', 'priority' => 1, ], ], //define custom guards here 'guard_manager' => [], //register custom guards providers here 'guards_provider_manager' => [], //define which guard provider to use, along with its configuration //the guard provider should know how to build a list of GuardInterfaces based on its configuration 'guards_provider' => [ 'type' => 'ArrayGuards', 'options' => [ 'guards' => [ [ 'type' => 'Route', 'options' => [ 'rules' => [ 'premium' => ['admin'], 'login' => ['guest'], 'logout' => ['admin', 'user', 'viewer'], 'account' => ['admin', 'user'], 'home' => ['*'], ] ] ], [ 'type' => 'RoutePermission', 'options' => [ 'rules' => [ 'premium' => ['premium'], 'account' => ['my-account'], 'logout' => ['only-logged'], ] ] ], [ 'type' => 'Controller', 'options' => [ 'rules' => [ [ 'route' => 'controller route name', //list of actions to apply, or empty array for all actions 'actions' => [], //by default, authorization pass if all permissions are present (AND) //list of roles to allow 'roles' => [], ], ] ] ], [ 'type' => 'ControllerPermission', 'options' => [ 'rules' => [ [ 'route' => 'controller route name', //list of actions to apply, or empty array for all actions 'actions' => [], //by default, authorization pass if all permissions are present (AND) //list of permissions to allow 'permissions' => [], ], [ 'route' => 'controller route name', //list of actions to apply, or empty array for all actions 'actions' => [], 'permissions' => [ //permission can be defined in this way too, for all permission type guards //list of permissions 'permissions' => [], 'condition' => \Dot\Rbac\Guard\GuardInterface::CONDITION_OR, ] ] ] ] ] ] ], ], //overwrite default messages 'messages_options' => [ 'messages' => [ //MessagesOptions::UNAUTHORIZED => 'You must sign in first to access the requested content', //MessagesOptions::FORBIDDEN => 'You don\'t have enough permissions to access the requested content', ] ], ], ];
Register the RbacGuardMiddleware in the pipe
The last step to use this package is to register the middleware.
This middleware triggers the authorization event.
You MUST insert this middleware between the routing middleware and the dispatch middleware of the application, because the guards need the RouteResult in order to get the matched route and params.
middleware-pipeline.global.php
//... 'routing' => [ 'middleware' => [ ApplicationFactory::ROUTING_MIDDLEWARE, //... \Dot\Rbac\Guard\Middleware\RbacGuardMiddleware::class, //... ApplicationFactory::DISPATCH_MIDDLEWARE, ], 'priority' => 1, ], //...
dotkernel/dot-rbac-guard 适用场景与选型建议
dotkernel/dot-rbac-guard 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 24.33k 次下载、GitHub Stars 达 4, 最近一次更新时间为 2016 年 09 月 22 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「authorization」 「Authentication」 「rbac」 「laminas」 「mezzio」 「rbac-guard」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 dotkernel/dot-rbac-guard 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 dotkernel/dot-rbac-guard 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 dotkernel/dot-rbac-guard 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Automatically logs-in users if they are already authenticated by a remote source. (e.g. environment variable REMOTE_USER)
GraphQL authentication for your headless Craft CMS applications.
Ory-Hydra OAuth 2.0 Client Provider for The PHP League OAuth2-Client
A lightweight and powerful OAuth 2.0 authorization and resource server library with support for all the core specification grants. This library will allow you to secure your API with OAuth and allow your applications users to approve apps that want to access their data from your API.
Laravel middleware to restrict a site or specific routes using HTTP basic authentication
Email Toolkit Plugin for CakePHP
统计信息
- 总下载量: 24.33k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 5
- 点击次数: 25
- 依赖项目数: 2
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2016-09-22