[SYNCOPE-307] Virtual Attributes don't propagated in case of update during synchronization

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.6, 1.1.0
• Fix Version/s: 1.0.6, 1.1.0
• Component/s: core
• Assignee: Fabio Martelli
• Reporter: Fabio Martelli
• Created: 04/Feb/13 11:48
• Updated: 27/Feb/13 09:08
• Resolved: 13/Feb/13 18:41

Description

UC:

• Suppose two resources A and B;
• Suppose to synchronize from A;
• Suppose to have virtual attributes mapped just on B;
• Suppose to retrieve a user to be updated locally and to be created new on B (thanks to an ad-hoc user template).

User will be updated locally and created on B but its virtual attribute values won't be propagated on B.

The bug is into the virtual attribute management during sync and propagation: in the UC provided above, the 'populate' method of the class AttributableOperations will never provide virtual attributes to be used by SyncJob to create the update propagation task.

Issue Links

• is blocked by: SYNCOPE-154 Virtual attribute cache