[ https://issues.apache.org/jira/browse/SYNCOPE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641011#comment-13641011 ]
Hudson commented on SYNCOPE-357: -------------------------------- Integrated in Syncope-trunk #202 (See [https://builds.apache.org/job/Syncope-trunk/202/]) [SYNCOPE-357] Merge from 1_1_X (Revision 1471477) Result = SUCCESS ilgrosso : Files : * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/RoleController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/RoleDataBinder.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java > When deleting role on external resource, also remove from there users with > resource assigned only via that role > --------------------------------------------------------------------------------------------------------------- > > Key: SYNCOPE-357 > URL: https://issues.apache.org/jira/browse/SYNCOPE-357 > Project: Syncope > Issue Type: Bug > Affects Versions: 1.1.0 > Reporter: Francesco Chicchiriccò > Assignee: Francesco Chicchiriccò > Fix For: 1.1.1, 1.2.0 > > > Scenario: > * resource RES with mapping for both users and roles > * role ROLE with RES assigned > * user USER with role ROLE assigned, and no RES assigned for other reasons > (directly or via another role) > As result, USER is present on the physical resource represented by RES (e.g. > an actual LDAP server, for example). > When removing ROLE from Syncope, ROLE is also removed from the physical > resource represented by RES, while USER is not removed from the physical > resource: this must be fixed, USER is needed to be also removed from there. > If, instead, USER has RES assigned directly or via another role, no action > must be performed onto the physical resource. -- 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