Optional Expiration for Roles and Permissions

[eramitgupta]

Hi mate 👋, @Houbsi and @herovish143,

I wanted to bring your attention to this pull request regarding Optional Expiration for Roles and Permissions. Could you please take a look and provide your feedback? Your insights would be greatly appreciated!

Thank you!

[Houbsi]

The new naming scheme {model}-{action} should be implemented. You did it before i added the change.

[eramitgupta]

The PR was merged

[Houbsi]

I had a quick read through @eramitgupta made some comments about the logic. From Code side i didn't find anything during my quick readthrough.

[eramitgupta]

Optional Expiration for Roles and Permissions

If you want to add something to it, please let me know
or if there is any bug

This Laravel package introduces an optional expiration feature for roles and permissions, allowing developers to assign roles and permissions to users with a specified expiration date. This functionality provides greater control over user access, enabling you to manage permissions dynamically based on your application's needs.

Features

• Optional Expiration Dates: When assigning roles or permissions, you can optionally specify an expiration date. If no expiration date is provided, the role or permission remains active indefinitely.

• Flexible Management: Users can have multiple roles and permissions, each with its own expiration date. This allows for granular control over user access based on changing requirements or time-limited privileges.

• Automatic Expiration Handling: The system automatically checks if a role or permission has expired. If a role or permission is expired, it will be considered inactive, preventing access to protected resources.

Usage

To assign a role or permission with an expiration date, you can use the following methods:

php artisan erag:new-update  

Refer to the RolePermissionSeeder.php.stub for examples.

Setting Expiration

If you don’t need an expiration, simply store null in the database:

/**
 * Use as needed.
 * 
 * Example usages:
 * - now()->subDays(2) // Subtract 2 days from the current date
 * - now()->addDays(1) // Add 1 day to the current date
 * - now()->addHours(2) // Add 2 hours to the current date
 * - now()->addMinutes(5) // Add 5 minutes to the current date
 */

To check if a user has a valid role or permission, the system will automatically verify if the current date is less than the expiration date:

if (auth()->user()->hasRole('admin')) {
    dd('yes');
} else {
    dd('no'); // This should display if the role has expired
}
  
if (auth()->user()->can('create-post')) {
    dd('You are allowed to access');
} else {
    dd('You are not allowed to access');
}

if (auth()->user()->hasPermissions('create-post', 'post-edit')) {
    dd('You are allowed to access Permissions');
} else {
    dd('You are not allowed to access');
}

Benefits

• Dynamic Access Control: Easily manage user access based on time-limited roles and permissions.

• Improved Security: Reduce the risk of unauthorized access by setting expiration dates for roles and permissions.

• Simplified Role Management: Quickly adjust user permissions without the need for manual intervention when roles or permissions expire.

Conclusion

The optional expiration feature for roles and permissions enhances your application's security and flexibility, making it easier to manage user access based on evolving requirements. Use this feature to ensure that users only have access to the resources they need for the time they need them.