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

Hudson commented on SYNCOPE-354:
--------------------------------

Integrated in Syncope-1_1_X #25 (See 
[https://builds.apache.org/job/Syncope-1_1_X/25/])
    [SYNCOPE-354] ResourceOperation.DELETE not always resolve to delete() on 
connector, it might also become update() - removing the condition from 
LDAPMembershipSyncActions (Revision 1471403)

     Result = SUCCESS
ilgrosso : 
Files : 
* 
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java
* 
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/util/URIUtil.java
* 
/syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java

                
> LDAP Membership propagation does not remove memberships
> -------------------------------------------------------
>
>                 Key: SYNCOPE-354
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-354
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.1.0
>         Environment: n/a
>            Reporter: James Flemer
>            Assignee: Francesco Chicchiriccò
>              Labels: delete, ldap, propagation, role
>             Fix For: 1.1.1, 1.2.0
>
>
> Configure a LDAP connector and resource, use the 
> LDAPMembershipPropagationActions propagator class, add a LDAP role to a user, 
> then try to remove that role.  The role is removed in Syncope but not LDAP; 
> the next sync will add it back in Syncope.
> In LDAPMembershipPropagationActions, line 75 (Syncope 1.1.0), there is a 
> conditional on:
>     ResourceOperation.DELETE != task.getPropagationOperation
> So LDAPMembershipPropagationActions refuses to process any delete operations.
> Should the operation be DELETE here (vs UPDATE)?  If so, 
> LDAPMembershipPropagationActions needs to deal with DELETE appropriately.

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