[
https://issues.apache.org/jira/browse/SYNCOPE-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14053464#comment-14053464
]
Francesco Chicchiriccò commented on SYNCOPE-531:
------------------------------------------------
[~wimmelg], the changes you made look fine to me - I have also [merged the
changes|http://svn.apache.org/r1608371] into the new 1_2_X branch (I will also
merge into the trunk as soon as SYNCOPE-532 is fixed).
To me you can resolve this issue.
> Failed login counter not reset if log.lastlogindate==false
> ----------------------------------------------------------
>
> Key: SYNCOPE-531
> URL: https://issues.apache.org/jira/browse/SYNCOPE-531
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.1.8, 1.2.0
> Reporter: Guido Wimmel
> Assignee: Guido Wimmel
> Priority: Minor
> Fix For: 1.1.9, 1.2.0
>
>
> The failed login counter SyncopeUser.getFailedLogins() is not set to zero on
> successful login if log.lastlogindate==false is set in the configuration. In
> particular, AuthenticationTestITCase.checkFailedLogins() fails if content.xml
> is modified such that log.lastlogindate==false.
> See also the discussion in SYNCOPE-507.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
