[
http://jira.magnolia.info/browse/MAGNOLIA-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17318#action_17318
]
Jan Haderka commented on MAGNOLIA-1355:
---------------------------------------
* One way to fix this would be to ask user if (s)he wants to activate changes
immediately while changing the password. At this moment we should be able to
still use the old password while having new one stored already.
* Other option would be to use workflow and let superuser to activate such
changes on behalf of users ... wouldn't work for the superuser himself though.
> Changing the password of the current user does not allow activation
> -------------------------------------------------------------------
>
> Key: MAGNOLIA-1355
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1355
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.0.1
> Environment: Magnolia 3.0.1 Enterprise
> JBoss AS 4.0.5GA
> Reporter: Amir Mistric
> Assignee: Jan Haderka
>
> 1. Log in as superuser on author
> 2. Change the password for a superuser
> 3. Activate the superuser user (to propagate changes to public instance)
> --> You get an JS alert error "Can't Activate...."
> I guess because Magnolia uses current user to log in to the subscribers, when
> you change your password authentication on remote subscribers fails....
> If that is the case, then there has to be a way to propagate the new password
> before the authentication occurs or use the old password, authenticate and
> then update subscribers...
--
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/
----------------------------------------------------------------
