syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-1153) Push Tasks result to show "no operation" when operation is not enabled
Date Wed, 12 Jul 2017 13:43:00 GMT

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

ASF subversion and git services commented on SYNCOPE-1153:
----------------------------------------------------------

Commit f191fd00284c345cae1002c5989d780c3d6daa5f in syncope's branch refs/heads/2_0_X from
[~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f191fd0 ]

[SYNCOPE-1158][SYNCOPE-1153] Better PushTask reports


> Push 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: core
>    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
>            Assignee: Francesco Chicchiriccò
>            Priority: Minor
>             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)

Mime
View raw message