Analysis of practical PHP member permission control implementation principles_PHP tutorial

My general permission system design is to try not to involve code modification when changing permissions. It comes from the chinaunix forum. I turned it over today to take a look. I hope it will be helpful to everyone and will be a great improvement for bkJia friends.

Copy code The code is as follows:

/*
　 *Control access table
　* Acl value function
* 1 Requires login
* 2 Self-modification
* 4 Requires group permission set
* 8 Requires identity access set
🎜>　* 64 Accessible Sundays
　* 128 Accessible times
　* 256 Enter password to access
　* 512 Super management use
　*/
　class aclACL extends acl {
Public $routername="acl";
public $aclid='2'; //Permission resource ID, if the logged-in person does not have this permission, then the other values ​​​​(below) are 0 and cannot be accessed
public $roledisable=array(9); //Disable identity
public $pwd=123456; //Password access ACL->noPwd();
public $date=array('begin'=>0 ,'end'=>0); //Allow dates between
public $hours=array('begin'=>0,'end'=>0); //Hour range within a day
Public $weeks=array('begin'=>0,'end'=>0); //Monday to Saturday within a week
public $aclgroup=array("create"=>"4, 45,8"); //create requires groups to create
public $aclrole=array("all"=>"6","create"=>"7,95,78"); // Create requires the role to be created. This group requires the role with ID 6 to access
public $acl=array("all"=>0,
"index"=>4, //Table 4 Indicates the combination of inspection groups
　"delete"=>1, //Delete can only be deleted after logging in, of course it can be set to 2 or 4
　"update"=>1, //Update submission can only be done by logging in It can be updated after doing it here to prevent illegal and post. Edit cannot access the display edit content page
　"createForm"=>1, //It is also impossible to submit a new database
　"edit"=>0, //The edit box is displayed only after logging in
　"show"=>0, //It can be displayed without logging in
　"create"=>1); //Innovation forms require login operations and can set a certain group to be able to Create
　}
　?>
　

This is the file module to be authenticated is acl

Whenever a user accesses the acl module, if authentication is turned on, this class will be called
Then this class will perform authentication checks based on the value of all or index of $acl.
Just put this file in the router/acl directory. The framework will automatically authenticate. If the user does not have the corresponding forward authorization, he will not be able to access the corresponding restrictions.
For example, the negative permission of the crud create method is 17. According to the previous explanation, login and group authorization should be required, which are the three groups 4 45 8 of create in the $aclgroup array.
First, if the member is not logged in, he will be prompted to log in. If the member is not logged in, he will be prompted to log in. If you are not in these three groups and cannot access this method, you will be prompted that you do not have permission.
At present, the router can enable acl control according to the situation
The method is to add public function isAcl(){} in the xxxxRouter.class.php file
You can return the permission file name, such as returning curd, then it will be called automatically curdACL.class.php class and name
CurdRouter class setting verification

Copy code The code is as follows:

class curdRouter extends controller{

　 //Return to RBAC control access list verification class. By default, it has the same name as the router, which is curd
　 //You can not write this function, then the universal permission system will not be enabled.
public function isAcl(){}
public function index()
{
$booktype=M("booktype");
$this->pager=C("pager" ); //Get the category
$this->pager->setPager($booktype->count(),10,'page');//Get the total number of data, set each page to 10
$this->assign("list",$booktype->orderby("bookid desc")->limit($this->pager->offset(),10)->fetch() ->getRecord());
　}
　public function login(){ //Login page
　}
　public function logout(){ //Exit page
　MY()-> ;logout(); //Log out
　redirect(url_for("guestbook/index"),"Logout successful",3);
　}
　public function noAcl($mask) { //Process it If there is no permission, redirect to login
redirect(url_for("guestbook/login"),"Login required",3);
}
public function loginpost() { //Login submission place simply handles login authentication
　if($_POST['author']=='queryphp'&&md5($_POST['pwd'])==md5('123456'))
　{
　MY()->setLogin (); //Set login status
redirect(url_for("guestbook/adminlist"),"Login successful",3);
　}
redirect(url_for("guestbook/login"),"Login Failed",3);
　}

Copy code The code is as follows:

　 /*
* Basic login information class
* Permission table can be cached Data is restored when logging in.
　*/
　class mybase {
　public $options=array();
　public $uid;
　public $username;
　public $isadmin;
　public $role= array(); //The identity I use
public $group=array(); //The group I am in
public $grouprole=array(); //The identity of the group
public $mygroupMar=array (); //The group I own and manage
public $mygroupOwn=array(); //The group that belongs to me
public $acl=array(); // Active control table groupacl and myacl control permission collection content It is rbacid of rbac
public $groupacl=array(); //Control permissions owned by the group
public $myacl=array(); //Control permissions owned by my identity
public $loginfaild =0; //If the number of failed logins exceeds this number, how many minutes should the IP login be banned?

This is basic
You can put myUser.class.php in the project lib directory
Copy the code and use the MY() function to get myUser.

　

　

You can view the framework file

There is a guestbookRouter.class.php in the project/router directory

In the background

　

Get the guestbookRouter.class.php class name and method.

Then add permissions to these methods

　

There is an application permission on the right and a cancellation permission. If you cancel the permission, it means there is no permission restriction

That is to delete the permission file

Apply permissions means adding permissions to this class will generate a permissions file.

Generate the guestbookACL.class.php file in project/router/acl/

When the program loads guestbookRouter.class.php, it will check whether there is a guestbookACL.class.php permission file

If yes, use permission verification, if not, then no. Adding and subtracting permissions in this way does not change the entry of the guestbookRouter.class.php file

So it will be very convenient to add permissions in the future.
http://queryphp.googlecode.com/files/queryphp_2011_01_27.zip

http://www.bkjia.com/PHPjc/323443.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/323443.htmlTechArticleMy general permission system design is to try not to involve code modification when changing permissions. It comes from the chinaunix forum and is transferred here today. have a look. I hope it will be helpful to everyone. For friends with PHP100...