[
https://issues.apache.org/jira/browse/SYNCOPE-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-1153:
--------------------------------------------
Fix Version/s: 2.1.0
2.0.5
> Tasks result to show "no operation" when operation is not enabled
> ------------------------------------------------------------------
>
> Key: SYNCOPE-1153
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1153
> Project: Syncope
> Issue Type: Improvement
> Components: console
> Affects Versions: 2.0.4
> Environment: I will use the default demo for embedded mode using the
> ApacheDS and LDAP push provision as the use case but I think the same occurs
> with other connectors.
> Reporter: Filipe Silva
> Fix For: 2.0.5, 2.1.0
>
>
> After starting the embedded mode I create a push task for the
> resource-ldap-orgunit (only name is necessary) and I choose execute that task
> (by default the operations 'Allow create/update/delete/syncstatus' are
> disabled).
> The result status of the execution shows
> {noformat}
> Realms [created/failures]: 3/0 [updated/failures]: 0/0 [deleted/failures]:
> 0/0 [no operation/ignored]: 0/0
> Realms created:
> CREATE SUCCESS (key/name): 722f3d84-9c2b-4525-8f6e-e4b82c55a36c//odd
> CREATE SUCCESS (key/name): c5b75db1-fce7-470f-b780-3b9934d82a9d//even
> CREATE SUCCESS (key/name): 0679e069-7355-4b20-bd11-a5a0a5453c7c//even/two
> {noformat}
> In the LDAP no new organizationalUnit appears
> I think it should show "no operation" to show a distinct output result than
> when "Allow create/update/delete/syncstatus" are enabled and the
> organizationalUnits were really created in the resource (LDAP).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
