[ https://issues.apache.org/jira/browse/SYNCOPE-665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734708#comment-14734708 ]
ASF subversion and git services commented on SYNCOPE-665: --------------------------------------------------------- Commit 00988759750f53f6737ef7d50e7faf63192257fa in syncope's branch refs/heads/master from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=0098875 ] [SYNCOPE-665] Implementation completed > Introduce LogicActions for users and groups > ------------------------------------------- > > Key: SYNCOPE-665 > URL: https://issues.apache.org/jira/browse/SYNCOPE-665 > Project: Syncope > Issue Type: Improvement > Reporter: Francesco Chicchiriccò > Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > As known, Syncope can be triggered in two different ways: > # via REST (which in turns invokes the Loigc layer - formerly Controller > layer) > # via scheduled synchronization (e.g. by creating and running `SyncTask` > instances) > While for the latter it is indeed possible to define user / group *templates* > - which serves as default for entities being created or updated - and also > [SyncActions|https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass], > the former instead defines {{AttributableTransformer}}, which is way less > handy. > The idea is to enable for REST invocation a set of features similar to what > already provided for synchronization., e.g. to introduce: > # the {{LogicActions}} interface > # evaluation of user / group templates during relevant Logic methods call > Such new entities will be linked to [realms|SYNCOPE-119] and thus involved in > their inheritance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)