You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/11/06 11:01:27 UTC

[jira] [Commented] (SYNCOPE-725) Derived attributes management refactoring

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

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

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

[SYNCOPE-725] Refactoring completed


> Derived attributes management refactoring
> -----------------------------------------
>
>                 Key: SYNCOPE-725
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-725
>             Project: Syncope
>          Issue Type: Improvement
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.0.0
>
>
> Similarly to SYNCOPE-709 with virtual, change the way how derived attributes are handled; in particular
>  # derived attributes are not assigned any more to users (groups, any objects) but, as long as an user (group, any object) is assigned the AnyTypeClass of which the derived schema is part, it is also assigned the related derived attribute
>  # derived attributes can only be mapped for propagation, not synchronization



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)