Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Tue, 24 Jan 2012 01:11:51 +0000 (UTC)
From: "Les Hazlewood (Closed) (JIRA)" <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: 
 <652529487.69702.1327367511555.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <4278116.12211295262053623.JavaMail.jira@thor>
Subject: [jira] [Closed] (SHIRO-237) nullpointer error at permission check
 when no permissionresolver is set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/SHIRO-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Les Hazlewood closed SHIRO-237.
-------------------------------


Closing with the 1.2.0 release.
                
> nullpointer error at permission check when no permissionresolver is set
> -----------------------------------------------------------------------
>
>                 Key: SHIRO-237
>                 URL: https://issues.apache.org/jira/browse/SHIRO-237
>             Project: Shiro
>          Issue Type: Bug
>          Components: Realms 
>    Affects Versions: 1.1.0
>         Environment: all
>            Reporter: Korbinian Bachl
>            Assignee: Kalle Korhonen
>            Priority: Critical
>             Fix For: 1.2.0
>
>
> in class AuthorizingRealm, the isPermitted( ... checks never look if the the permissionResolver are set but allways will query them in case a permission reqeust os asked for.
> Solutions: 
> 1. catch empty/ null permissionResolver in Authorizingrealm
> 2. force that all derived AuthorizingRealms have a permissionResolver by making this required in the constructor
> 3. defaultset the current only implementation (WildcardPermissionResolver) into the getPermissionResolver method so either this one is used or it has to be overwritten
> I would suggest 2. as its most clean and will fail/ force to be cared with at compiletime already.
> PS: this is the issue described in my mailing to list 
> http://mail-archives.apache.org/mod_mbox/shiro-user/201012.mbox/browser

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira