You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2013/10/25 11:58:34 UTC

[jira] [Updated] (ISIS-574) Upgrade isis-security-shiro to use shiro 1.2.2 (currently using 1.2.1)

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

Dan Haywood updated ISIS-574:
-----------------------------

    Fix Version/s: security-shiro-1.4.0

> Upgrade isis-security-shiro to use shiro 1.2.2 (currently using 1.2.1)
> ----------------------------------------------------------------------
>
>                 Key: ISIS-574
>                 URL: https://issues.apache.org/jira/browse/ISIS-574
>             Project: Isis
>          Issue Type: Improvement
>          Components: Security: Shiro
>    Affects Versions: security-shiro-1.1.1
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: security-shiro-1.4.0
>
>
> On attempting to upgrade our dependency on Shiro to the latest (1.2.2), found that our the unit tests, at least, do not pass.
> The reason seems to be that our globally registered IsisPermissionResolver, in shiro.ini is not picked up, and so IsisPermission is not used to interpret the permission strings (Shiro's default WildcardPermission is used instead).
> Not clear at this point whether the issue lies with Shiro, or with Isis misconfiguring Shiro (in a way that used to work).



--
This message was sent by Atlassian JIRA
(v6.1#6144)