You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Andrea Patricelli (JIRA)" <ji...@apache.org> on 2013/07/16 11:44:49 UTC
[jira] [Created] (SYNCOPE-402) Inconsistent status of user edit
form after exception returned by bad propagation on primary resource
Andrea Patricelli created SYNCOPE-402:
-----------------------------------------
Summary: Inconsistent status of user edit form after exception returned by bad propagation on primary resource
Key: SYNCOPE-402
URL: https://issues.apache.org/jira/browse/SYNCOPE-402
Project: Syncope
Issue Type: Improvement
Components: console
Affects Versions: 1.1.3, 1.1.2
Reporter: Andrea Patricelli
Fix For: 1.1.4
During creation (and save) of user to be propagated on a primary resource, if propagation fails (due to an error) it returns a propagation exception to console and to user edit form, which goes in an inconsistent status and stucks.
A possible solution is to go directly, in case of propagation exception, to summary page reporting propagation status on resource(s); in particular propagation signaling icon of failure may be abled to show exception message caught from PropagationStatusTO.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira