🐇 An Authorization Library for Webman Plugin 🐇

An authorization library that supports access control models like ACL, RBAC, ABAC for Webman plugin.

• Installation
• Configuration
  • Dependency Injection
  • Database Configuration
• Usage
• Multiple Driver Configuration
• Tutorials
• Testing
• Contributing
• Credits
• Troubleshooting

Install the package via Composer:

composer require -W casbin/webman-permission

Modify the config/container.php configuration file as follows:

$builder = new \DI\ContainerBuilder();
$builder->addDefinitions(config('dependence', []));
$builder->useAutowiring(true);
return $builder->build();

By default, the policy storage uses ThinkORM.

The default uses ThinkORM. Modify the database configuration in config/thinkorm.php.

Note: If using Laravel database, configure as follows:

• Modify the database configuration in config/database.php
• Change the adapter in config/plugin/casbin/webman-permission/permission.php to the Laravel adapter

Execute the following SQL to create the policy rules table:

CREATE TABLE `casbin_rule` (
    `id` BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT,
    `ptype` VARCHAR(128) NOT NULL DEFAULT '',
    `v0` VARCHAR(128) NOT NULL DEFAULT '',
    `v1` VARCHAR(128) NOT NULL DEFAULT '',
    `v2` VARCHAR(128) NOT NULL DEFAULT '',
    `v3` VARCHAR(128) NOT NULL DEFAULT '',
    `v4` VARCHAR(128) NOT NULL DEFAULT '',
    `v5` VARCHAR(128) NOT NULL DEFAULT '',
    PRIMARY KEY (`id`) USING BTREE,
    KEY `idx_ptype` (`ptype`) USING BTREE,
    KEY `idx_v0` (`v0`) USING BTREE,
    KEY `idx_v1` (`v1`) USING BTREE,
    KEY `idx_v2` (`v2`) USING BTREE,
    KEY `idx_v3` (`v3`) USING BTREE,
    KEY `idx_v4` (`v4`) USING BTREE,
    KEY `idx_v5` (`v5`) USING BTREE
) ENGINE = INNODB CHARSET = utf8mb4 COMMENT = 'Casbin Policy Rules Table';

Configure your Redis settings in config/redis.php.

# Restart in foreground
php start.php restart

# Or restart in daemon mode
php start.php restart -d

After successful installation, you can use the library as follows:

use Casbin\WebmanPermission\Permission;

// Add permissions to a user
Permission::addPermissionForUser('eve', 'articles', 'read');

// Add a role for a user
Permission::addRoleForUser('eve', 'writer');

// Add permissions to a role
Permission::addPolicy('writer', 'articles', 'edit');

if (\Casbin\WebmanPermission\Permission::enforce('eve', 'articles', 'edit')) {
    echo 'Congratulations! Permission granted.';
} else {
    echo 'Sorry, you do not have access to this resource.';
}

You can use multiple driver configurations:

$permission = \Casbin\WebmanPermission\Permission::driver('restful_conf');

// Add permissions to a user
$permission->addPermissionForUser('eve', 'articles', 'read');

// Add a role for a user
$permission->addRoleForUser('eve', 'writer');

// Add permissions to a role
$permission->addPolicy('writer', 'articles', 'edit');

// Check permissions
if ($permission->enforce('eve', 'articles', 'edit')) {
    echo 'Congratulations! Permission granted.';
} else {
    echo 'Sorry, you do not have access to this resource.';
}

For more API details, refer to the Casbin API Documentation.

• Casbin Permission Practice: Getting Started (Chinese)
• Casbin Permission Practice: RBAC Authorization Based on Roles (Chinese)
• Casbin Permission Practice: RESTful and Middleware Usage (Chinese)
• Casbin Permission Practice: Using Custom Matching Functions (Chinese)
• Webman Practice Tutorial: Using Casbin Permission Control (Chinese)

This project includes a comprehensive unit test suite covering the following aspects:

tests/
├── Adapter.php                    # Basic adapter tests
├── PermissionTest.php            # Permission class tests
├── AdapterTest.php               # Detailed adapter tests
├── EdgeCaseTest.php              # Edge case tests
├── IntegrationTest.php           # Integration tests
├── LaravelDatabase/
│   ├── LaravelDatabaseAdapterTest.php
│   └── TestCase.php
├── ThinkphpDatabase/
│   ├── DatabaseAdapterTest.php
│   └── TestCase.php
└── config/
    └── plugin/
        └── casbin/
            └── webman-permission/
                └── permission.php

1. Basic Functionality

   • Permission add, remove, check
   • Role assignment, removal
   • Policy management

2. Adapter Tests

   • Database operations
   • Filter functionality
   • Batch operations
   • Transaction handling

3. Edge Cases

   • Null value handling
   • Special characters
   • Large data volumes
   • Performance testing

4. Integration Tests

   • Complete RBAC workflow
   • Domain permission control
   • Multi-driver support
   • Complex business scenarios

5. Error Handling

   • Exception scenarios
   • Invalid input
   • Concurrent access

# Run all tests
php vendor/bin/phpunit tests/

# Run specific test file
php vendor/bin/phpunit tests/PermissionTest.php

# Run specific test method
php vendor/bin/phpunit --filter testAddPermissionForUser tests/PermissionTest.php

# Generate coverage report
php vendor/bin/phpunit --coverage-html coverage tests/

• PHP >= 8.1
• PHPUnit >= 9.0
• Database connection
• Redis connection

The test environment automatically creates the following tables:

• casbin_rule - Default policy table
• other_casbin_rule - Other driver policy table

1. Writing New Tests

   • Inherit from appropriate test base classes
   • Follow naming conventions
   • Add necessary assertions

2. Test Data Management

   • Use setUp() and tearDown() methods
   • Ensure test data isolation
   • Clean up test data

3. Test Coverage

   • Cover normal workflows
   • Test exception scenarios
   • Verify boundary conditions

1. Write corresponding test cases for new features
2. Ensure test coverage meets requirements
3. Run the complete test suite
4. Check test status before submitting code

1. Write reproduction tests for bugs
2. Verify tests pass after fixing bugs
3. Ensure existing functionality is not affected

Built on top of Casbin. For full documentation, visit the official website.

composer remove php-di/php-di

if (is_null(static::$_manager)) {
    static::$_manager = new Enforcer($model, Container::get($config['adapter']), false);
}

if (is_null(static::$_manager)) {
    if ($config['adapter'] == DatabaseAdapter::class) {
        $_model = new RuleModel();
    } elseif ($config['adapter'] == LaravelDatabaseAdapter::class) {
        $_model = new LaravelRuleModel();
    }
    static::$_manager = new Enforcer($model, new $config['adapter']($_model), false);
}

Error: Call to a member function connection() on null

Solution: Check if your local database proxy is working correctly. Using Docker container host addresses like dnmp-mysql may cause this issue.

MIT License