Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 86BF9200CFE for ; Fri, 8 Sep 2017 15:43:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8572E1609BD; Fri, 8 Sep 2017 13:43:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CB9FB1609A7 for ; Fri, 8 Sep 2017 15:43:03 +0200 (CEST) Received: (qmail 97628 invoked by uid 500); 8 Sep 2017 13:43:02 -0000 Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@syncope.apache.org Delivered-To: mailing list dev@syncope.apache.org Received: (qmail 97617 invoked by uid 99); 8 Sep 2017 13:43:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Sep 2017 13:43:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5CA0518FD5B for ; Fri, 8 Sep 2017 13:43:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id zKmPrG2yfL2u for ; Fri, 8 Sep 2017 13:43:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 63EE460D9C for ; Fri, 8 Sep 2017 13:43:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E8114E0635 for ; Fri, 8 Sep 2017 13:43:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9FBCF24147 for ; Fri, 8 Sep 2017 13:43:00 +0000 (UTC) Date: Fri, 8 Sep 2017 13:43:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: dev@syncope.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SYNCOPE-1206) Dynamic membership updates not considered for provisioning during update MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 08 Sep 2017 13:43:04 -0000 [ https://issues.apache.org/jira/browse/SYNCOPE-1206?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 158648#comment-16158648 ]=20 ASF subversion and git services commented on SYNCOPE-1206: ---------------------------------------------------------- Commit 34a3456e866eee91cf898f2fef5885332509ee84 in syncope's branch refs/he= ads/2_0_X from [~ilgrosso] [ https://git-wip-us.apache.org/repos/asf?p=3Dsyncope.git;h=3D34a3456 ] [SYNCOPE-1206] At the end of update, explicitely process dynamic membership= s for group resources > Dynamic membership updates not considered for provisioning during update > ------------------------------------------------------------------------ > > Key: SYNCOPE-1206 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1206 > Project: Syncope > Issue Type: Bug > Components: core > Affects Versions: 2.0.5 > Reporter: Francesco Chicchiricc=C3=B2 > Assignee: Francesco Chicchiricc=C3=B2 > Fix For: 2.0.6, 2.1.0 > > > Let's suppose there is a group G with dynamic membership condition define= d and resource R assigned, and a user U which is not member of G neither st= atically nor dynamically. > If U is updated to match the dynamic condition of G, then U should be pro= pagated to R, but this does not happen currently. > If, afterwards, U is updated again to not match any more the dynamic cond= ition of G, then U should be removed from R, but this does not happen as we= ll. -- This message was sent by Atlassian JIRA (v6.4.14#64029)