rights Follow @yiiframework

I have asked the question stated below yesterday:

"problem in rights

I am giving rights for 'create' to the 'authenticated' but the 'guest' also get the same right.Means the extension does not undersatnd any difference between 'authenticated' and the 'guest' please help me . I am dying.:( "

Well I found the answer after discussing this with my senior.

Well the problem is that as long as the "authenticated" role will be there there will not be any difference between the guest and the authenticated. you will have to change the name of the role "authenticated" to something else such as "registered" or anything else that you want.

****Well this may be considered as a bug. ****

There is a line in rightsmodule.php in the view of rights which has following code: * @property string the name of the guest role. */ public $authenticatedName = 'Authenticated';

how a guest name can be assigned as 'Authenticated'? I think here lies some problem.

So conclusion is that you must change the name of the authenticated role to something else for the smooth operation.

You need to add business rules for Guest: return Yii::app()->user->isGuest;

and Authenticated: return !Yii::app()->user->isGuest;

This should solve all your problems

I am giving rights for 'create' to the 'authenticated' but the 'guest' also get the same right.Means the extension does not undersatnd any difference between 'authenticated' and the 'guest' please help me . I am dying.:(

Hi,

I've just uploaded this extension, which provides methods to ensure compatibility for rights and yii-user.

Best regards, schmunk

Thanks!

I've almost missed it :)

auth extension

You should have install = false in your main config file

Sometimes when I left my page opened for 30 minutes or when I open the site after some hours, I have this error. How can I solve it? Thanks for help.

Hi Chris,

Thank you for developing Rights module. Can you tell me more about the current core problems with Rights? I used rights within my cms and it will be great if you can tell me the current core problems of Rights. I will do my best to implement it.

Thank you once again for Rights module.

It's been a while since I've been working on Rights. After the success of my Twitter Bootstrap extension I decided that it was time to develop a new module for permissions management using bootstrap. I've been working on my Auth extension, which is a modern and responsive user interface for Yii's authorization manager and it was released yesterday.

If you liked Rights, I'm sure that you will feel at home using Auth as well. It fixes some of the core problems in Rights and is both easier to use and extend. There is also a demo available.

Here's a link to the extension page: http://www.yiiframework.com/extension/auth

hi, I do all muy homework. but i get this when trying to install:

"There must be at least one superuser!"

any idea ? there is some data that should be in new tables ? Best Regards

Hi, I have implemented rights to support caching. You guys can check it here:

http://www.yiiframework.com/forum/index.php/topic/36116-rights-alternative/page__view__findpost__p__183254

If you have any ideas/suggestions, please tell me.

Cheers!

We needed checkAccess() to return true when the user has permission for "Foo.*" and the check is called with "Foo.bar", when not AuthItem exists for "Foo.bar".

This is our solution, maybe it helps anyone:

public function checkAccess($operation,$params=array(),$allowCaching=true)
    {
        if ($this->isSuperuser===true)
            return true;
 
        if($allowCaching && $params===array() && isset($this->_access[$operation]))
            return $this->_access[$operation];
        else
        {
            $checkOperation = $operation;
 
            if ((strpos($operation,'*') === false) && (strpos($operation,'.')))
            {
                //in case we have an operation without asterisk we try to check access on the task as fallback, too 
 
                $item = Yii::app()->getAuthManager()->getAuthItem($operation);
                if ($item === null)
                {               
                                        //no AuthItem exists for this operation, let's check access on the task instead
 
                    $operationArray = explode('.', $operation);
                    $operationArray[1] = '*';
                    $checkOperation = implode('.', $operationArray);
                }
            }
 
            return $this->_access[$operation]=Yii::app()->getAuthManager()->checkAccess($checkOperation,$this->getId(),$params);
        }
    }

You can easily change it to always fallback (no matter whether the operation AuthItem exists for other roles), when you remove the inner item check.

My site Lii.vn does not work, I config as the guide above. When I access myapp/rights -> error. (I config urlmanager already!)

there is not a way to set the accessRules for static pages (created with CViewAction), for instance if I want to allow access to my static pages only for authenticated users. The normal accessRules let me to specify an action but not a view. Tnx ;)

It sure feels weird promoting myself here, but I've written some small examples on bizrules and would like to share it with you guys:

bizrules examples (using rights module)

P.S.: it isn't really specific to the rights-extension but i really don't see any reason for anyone to roll their own rbac when there's cniskas version.

you done great job.. But one issue with changing the layout. Now it is using layout from app.views.layout.main but I just want to use current theme layout how can i do that one

Who use last yii 1.1.11 and got error

include($data-&gt;getAssignmentsText(CAuthItem.php) [<a href='function.include'>function.include</a>]: failed to open stream: No such file or directory

@fix https://github.com/yiisoft/yii/commit/05441abf04cd14fc379066ab54d8f86f0d3f0e8b

Assigning actions to roles becomes rather tedious when you start having 10+ roles. Is there a way to make that part of the interface cleaner?

I've had a very good experience with Rights, as I used it in a very user role based projects, and got chance to dig into into it quite often..

What I felt most was that things are not documented properly, so I've written a small blog about small things one can so which are required often..

"My blog post about Rights"

Yii: :app()->user->checkAccess() doesn't seem to be recursively going through all the nodes of the assignment tree...

Okay, I was missing this :

the iteration can stop with a positive result when Yii encounters in the hierarchy a so-called default role

from http://www.yiiframework.com/wiki/136/getting-to-understand-hierarchical-rbac-scheme/

(stupid me)

Cheers!