[ 
https://issues.apache.org/jira/browse/SYNCOPE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772888#comment-13772888
 ] 

Hudson commented on SYNCOPE-417:
--------------------------------

SUCCESS: Integrated in Syncope-trunk #451 (See 
[https://builds.apache.org/job/Syncope-trunk/451/])
[SYNCOPE-417] Merge from 1_1_X (ilgrosso: rev 1524938)
* /syncope/trunk
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java

                
> Users are made active when updating in NoOpWorkflowAdapter
> ----------------------------------------------------------
>
>                 Key: SYNCOPE-417
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-417
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1.3
>            Reporter: Jesse van Bekkum
>            Assignee: Francesco Chicchiriccò
>            Priority: Minor
>             Fix For: 1.1.4, 1.2.0
>
>         Attachments: NoOpUserWorkflowAdapter.java.patch
>
>
> When using the NoOpWorkflow adapter a user is always set to active when an 
> update is done, even if the user is suspended. This is undesirable, I think a 
> user should stay in the state it is.
> This can be fixed by changing this line (117/118 of NoOpWorkflowAdapter.java):
>         return new WorkflowResult<Map.Entry<Long, Boolean>>(
>                 new AbstractMap.SimpleEntry<Long, Boolean>(updated.getId(), 
> true), propByRes, "update");
> into this:
>         return new WorkflowResult<Map.Entry<Long, Boolean>>(
>                 new AbstractMap.SimpleEntry<Long, Boolean>(updated.getId(), 
> !user.isSuspended()), propByRes, "update");

--
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

Reply via email to