ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Borisov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7220) Web console: Unsaved changes on revert identity
Date Mon, 18 Dec 2017 03:54:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16294495#comment-16294495

Ilya Borisov commented on IGNITE-7220:

I think this happens because identity revertion API call can't be blocked by config screen
unsaved changes guard. A possible solution would be to leverage the state change mechanism
of uirouter in order to optionally block identity reversion by making a separate state responsible
for the API call, much like the logout is implemented right now.

> Web console: Unsaved changes on revert identity
> -----------------------------------------------
>                 Key: IGNITE-7220
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7220
>             Project: Ignite
>          Issue Type: Bug
>          Components: wizards
>            Reporter: Vasiliy Sisko
>            Assignee: Ilya Borisov
> # In admin panel select any user and execute "Become this user" action.
> # Open and change any config without save.
> # Click by "Revert you identity?" link
> # Click "Cancel" button on an unsaved changes confirmation dialog.
> Become this user mode is finished, but user data stay on opened screen and can be modified.
> On move to another page or refresh of page the data of current user is showed.

This message was sent by Atlassian JIRA

View raw message