[jira] [Commented] (SYNCOPE-111) Failure during role attribute propagation

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on SYNCOPE-111:
--------------------------------

Integrated in Syncope-linux #218 (See [https://builds.apache.org/job/Syncope-linux/218/])
    SYNCOPE-111 #comment in case of membership add/remove just resources indirectly linked to it was used to be considered (Revision 1362044)

     Result = SUCCESS
fmartelli : 
Files : 
* /incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/PropagationManager.java
* /incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java
* /incubator/syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/SchemaTest.java
* /incubator/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java
* /incubator/syncope/trunk/core/src/test/resources/content.xml

                
> Failure during role attribute propagation
> -----------------------------------------
>
>                 Key: SYNCOPE-111
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-111
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.0-incubating
>            Reporter: fabio martelli
>            Assignee: fabio martelli
>             Fix For: 1.0.0-incubating
>
>
> Let's considering a role with a certain attribute memberOf to be propagated towards the resource X assigned to the role.
> Creating a membership with this role the propagation works fine: memberOf will be propagated correctly ...
> But, removing the membership, if the user mustn't be removed from the resource (see SYNCOPE-108), the resource attribute mapped with memberOf won't be updated.
> Case:
> 1. create role A and role B with memberOf m1 and m2 respectively.
> 2. assign the same resource X to A and B and define a schema mapping for memberOf (suppose a multivalue resource attribute 'm')
> 3. create a user specifying two memberships: one form A and one for B
> 4. verify that the resource attribute 'm' has been valued with m1 and m2
> 5. modify the user profile just by removing a membership
> 6. ... resource profile won't be updated correctly: te resource attribute 'm' won't be updated (it should be valued with one single value, m1 or m2)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira