shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Demers (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SHIRO-277) JdbcRealm needs to be refactored
Date Tue, 12 Jul 2016 13:35:20 GMT

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

Brian Demers resolved SHIRO-277.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.3.0)
                   1.2.0

This was merged in 36a848ba30990dacdc13efcd5ed75b393dfa0fd5 (in 1.2.0)

> JdbcRealm needs to be refactored
> --------------------------------
>
>                 Key: SHIRO-277
>                 URL: https://issues.apache.org/jira/browse/SHIRO-277
>             Project: Shiro
>          Issue Type: Improvement
>          Components: Realms 
>    Affects Versions: 1.1.0
>            Reporter: Ilya Pyatigorskiy
>              Labels: patch, patch-with-test
>             Fix For: 1.2.0
>
>         Attachments: jdbcRealm.patch
>
>
> There are at least 2 obvious problems:
> 1) the javadoc for JdbcRealm.setPermissionsQuery suggests that the query is expected
to have 3 columns ("containing the fully qualified name of the permission class, the permission
name, and the permission actions (in that order)"), but the code actually looks only for 1
- permission actions on index 0
> 2) it doesn't support salt - checks only for password matching



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message