Difference between #7 and #8 of
How to setup RBAC with a php file

Revision #8 has been created by Steve Friedl on Dec 2, 2010, 6:55:44 PM with the memo:

Recommended the use of auth.txt to preview auth.php; added minor cleanups
« previous (#7) next (#9) »

Changes

Title unchanged

How to setup RBAC with a php file

Category unchanged

How-tos

Yii version unchanged

Tags unchanged

Authentication

Content changed

In this cookbook I will attempt to explain how to use the lightweight version of [Role-Based Access Control](http://www.yiiframework.com/doc/guide/topics.auth#role-based-access-control) using a php file. This version does not use database but a php file and is controlled by CPhpAuthManager class. ## Configuring the roles: ## By default when setting up this particular type of rbac Yii will look for any defined roles in a file named auth.php and located in protected/data/auth.php
 
For the
 - for sake of easiness I will  add anwe'll use the example of user rbacRBAC to the blog demo. 
 
>Info: Yii expects to read auth.php and get an array() out of it. So we need to create auth.php and return array(); Yii also needs to write to that file when changing roles so make sure to provide enough permission access to that file needed by the system. Next we dHOWEVER: since Yii rewrites the auth.php file into a form that's far more difficult to edit, it's a good idea to edit a **auth.txt** file, where you can format and comment properly, then copy it to auth.php when you're ready to try it. The first time Yii rewrites auth.php it will be apparent why you want to do this.
 
 
D
eclare some roles in our auth.phptxt file: ```php // protected/runtime/auth.txt
 
 
return array(     'reader' =>
 
  
array (     'type'=>CAuthItem::TYPE_ROLE,    'description'=>'Can only read a post',         'bizRules'=>'',
 
        'data'=>''
 
),     'commentor' =>
 
  
array (     'type'=>CAuthItem::TYPE_ROLE,     'description'=>'Can post a comment',         'bizRules'=>'',
 
        'data'=>''
 
 
),     'admin' =>
 
  
array (     'type'=>CAuthItem::TYPE_ROLE,     'description'=>'Can read a post and post a comment',  'children'=>array(   'reader','commentor',
 
         ),

 
        ),
 
        'bizRules'=>'',
 
        'data'=>''
),
);
```
[...]
The above code declares 3 different types of roles:

1 -
**reader** - this type of role can only read a post but not post any comments 2 - **commentor** - this role gives access only to the comments form section to post a comment. 3 - **admin** - which can read a post and post a comment (consists of both roles above). ## Configuring the accessRules(): ##
 
 
Now that we've setup our roles we should move to apply them in action. In this example I will only apply them to our PostController as below:
 
 
 
```php 
public function
The **bizRules** and **data** elements aren't needed by this role scheme, but CPhpAuthManager seems to require them (and it will fail without them).
 
 
Once you've edited the file, put it in place:
 
 
    $ cp auth.txt auth.php
 
    $ chmod a+w auth.php               _# make sure Apache can write to it_
 
 
If you have to make a change to the roles, do it in the .txt file and re-copy to auth.php
 
 
## Configuring the accessRules(): ##
 
 
Now that we've setup our roles we should move to apply them in action. In this example I will only apply them to our PostController as below:
 
 
 
```php 
// in protected/controllers/PostController.php
 
 
class PostController extends CController {
 
 
    public function filters()
 
    {
 
        return array(
 
            'accessControl'           // required to enable
accessRules() );
 
{}
 
    public function accessRules()
 
    {
 
return array(          array('allow', // allow readers only access to the view file         'actions'=>array('view'),         'roles'=>array('reader'),         ),
 
                );
),
 
 
            array('deny',   // deny everybody else
 
                'users' => array('*')
 
            )
);
 
}     ...
 
``` The above code should be pretty clear - allow user with 'reader' role access to the view action. NOTE: Yii accessRules default to **allow**, so the explicit deny is required if you want this behavior.
 
 
## Configuring our tbl_user in our database: ## Next we add an additional field to our tbl_user. We call that field role (varchar 30). We also need two user entries in this table. We already have the 'demo' one from the blog tutorial and add a 'test' one. In the 'demo' role field entery 'reader' as data and for 'test' enter 'admin' as a role.

## Assigning roles: ##
[...]
}
```

 
The code we have added to the original UserIdentity class is:  


```php
[...]
}
```
>Info: Please see comments at the end of the lines for explanation on what every line of code does. It is important to remember that it is good practice to check if a roles has already been assigned becuase Yii assignes roles and does not delete them until you call the revoke() function. In ca
nse you forget and try to re-assign a role Yii will return an error. Another important point is when you assign a role you must save it by calling Yii::app()->authManager->save();
[...]
```php
// protected/config/main.php
 
 
return array(
 
    ...
 
    
'components'=>array(      'authManager'=>array(           'class'=>'CPhpAuthManager', //       ),
 
),
'authFile' => 'path'                  // only if necessary
 
        ),
 
        ...
``` This basically activates the authorization Manager of the application and tells yYii that we want to use CPhpAuthManager class to take care of our accessControll. When you login Yii will assign a role to your user id. After you login open up the auth.php file and see that Yii has re-arranged it in the appropriate way. For the sake of testing our functionality we should now add some rbacRBAC check to our views/post/view.php:

```php
[...]
>Info: When the user logs out we need to delete the assigned role otherwise if you change that user's role while he is offline and when he comes back and logs in again he will end up with two roles: the old one and the new one! So we place the below code in our logout action in the SiteController:


 
```php // protected/controllers/SiteController.php
 
 
public function actionLogout()
{
$assigned_roles = Yii::app()->authManager->getRoles(Yii::app()->user->id); //obtains all assigned roles for this user id
[...]
[another related rbac approach](http://yiiframework.ru/doc/cookbook/ru/access.rbac.file)<br />

>Disclaimer: The above code works for me. I do not guarantee that it will work in all situations. If you need more complex
rbacRBAC structure use the DB one. I've read all posts in the forum RE rbacre: RBAC but none of them helped me so the above code has been discovered through trial & error. Use it on your own responsibility.
24 4
21 followers
Viewed: 68 384 times
Version: 1.1
Category: How-tos
Written by: bettor
Last updated by: Stageline
Created on: Feb 7, 2010
Last updated: 5 years ago
Update Article

Revisions

View all history