Mailing-List: contact dev-help@shiro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shiro.apache.org
Date: Fri, 18 May 2012 18:13:07 +0000 (UTC)
From: "Les Hazlewood (JIRA)" <jira@apache.org>
To: dev@shiro.apache.org
Message-ID: 
 <629433647.15246.1337364787447.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <528792154.15067.1337362870968.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (SHIRO-363) PasswordMatcher should support
 character arrays
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Les Hazlewood resolved SHIRO-363.
---------------------------------

    Resolution: Fixed

Fix and accompanying test case were committed to the 1.2.x branch and trunk
                
> PasswordMatcher should support character arrays
> -----------------------------------------------
>
>                 Key: SHIRO-363
>                 URL: https://issues.apache.org/jira/browse/SHIRO-363
>             Project: Shiro
>          Issue Type: Bug
>          Components: Authentication (log-in)
>    Affects Versions: 1.2.0
>            Reporter: Les Hazlewood
>             Fix For: 1.2.1, 1.3.0
>
>
> The JdbcRealm by default returns a character array as its stored credentials.  The PasswordMatcher should automatically convert any saved character arrays to a String for use with the PasswordService.

--
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