[jira] [Updated] (SYNCOPE-417) Users are made active when updating in NoOpWorkflowAdapter
[ https://issues.apache.org/jira/browse/SYNCOPE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-417: --- Fix Version/s: 1.2.0 1.1.4 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.2 Reporter: Jesse van Bekkum Priority: Minor Fix For: 1.1.4, 1.2.0 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 WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), true), propByRes, update); into this: return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, 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
[jira] [Updated] (SYNCOPE-417) Users are made active when updating in NoOpWorkflowAdapter
[ https://issues.apache.org/jira/browse/SYNCOPE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-417: --- Affects Version/s: (was: 1.1.2) 1.1.3 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 Priority: Minor Fix For: 1.1.4, 1.2.0 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 WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), true), propByRes, update); into this: return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, 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
[jira] [Updated] (SYNCOPE-417) Users are made active when updating in NoOpWorkflowAdapter
[ https://issues.apache.org/jira/browse/SYNCOPE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jesse van Bekkum updated SYNCOPE-417: - Attachment: NoOpUserWorkflowAdapter.java.patch Patch for this issue 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 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 WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), true), propByRes, update); into this: return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, 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