[
https://issues.apache.org/jira/browse/SYNCOPE-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026222#comment-16026222
]
ASF subversion and git services commented on SYNCOPE-1099:
----------------------------------------------------------
Commit ca0fcf1b728c9c6937b55fd0a8bead1d91d3edb4 in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=ca0fcf1 ]
[SYNCOPE-1099] Adding checks to ensure that all resources (including the ones
coming from dynamic groups) are considered for propagation
> Dynamic group membership do not trigger propagation
> ---------------------------------------------------
>
> Key: SYNCOPE-1099
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1099
> Project: Syncope
> Issue Type: Bug
> Affects Versions: 2.0.3
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> Syncope supports from its early days the so-called group-based provisioning,
> e.g. members of group G, with G having resource R assigned, are considered
> for propagation to R.
> This mechanism works fine for static group assignment (e.g. an administrator
> assigns U to G) but not for dynamic group assignment (e.g. the dynamic
> condition for G matches U).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
