[
http://jira.magnolia.info/browse/MAGNOLIA-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Haderka resolved MAGNOLIA-2416.
-----------------------------------
Resolution: Fixed
Changing client side javascript posed some undesired side effects (circular
validation) as well as forcing both fields to be filled all the time. Solved by
implementing server side validation for DialogPassword. Seems to be safer way
to handle things like changing password since its behaviour can be easily
tested and can't be bypassed by the client.
Added tests for the validation.
trunk - r18937, r18938, 3.6 branch - r18939.
> Changing users password is possible without filling in the confirmation field.
> ------------------------------------------------------------------------------
>
> Key: MAGNOLIA-2416
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2416
> Project: Magnolia
> Issue Type: Bug
> Components: admininterface
> Affects Versions: 3.0.5, 3.5.9, 3.6.3
> Reporter: Bert Leunis
> Assignee: Jan Haderka
> Priority: Blocker
> Fix For: 3.6.x, 3.7
>
>
> When changing the password for superuser, we did not fill in the second
> field. It stayed blank, but we could still save the userinfo. So when you
> make an error in typing the password, you could lose the entry to magnolia as
> superuser. Doesn't seem to be very handy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
