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 5AD38200CF7 for ; Mon, 4 Sep 2017 10:00:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 597A5163815; Mon, 4 Sep 2017 08:00:29 +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 A0FE11635BD for ; Mon, 4 Sep 2017 10:00:28 +0200 (CEST) Received: (qmail 4913 invoked by uid 500); 4 Sep 2017 08:00:27 -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 4900 invoked by uid 99); 4 Sep 2017 08:00:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2017 08:00:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 5EC6CC1A6F for ; Mon, 4 Sep 2017 08:00:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-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 (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YpP6Vqks4F6K for ; Mon, 4 Sep 2017 08:00:26 +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 22FA86127B for ; Mon, 4 Sep 2017 08:00:26 +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 A3381E0EF8 for ; Mon, 4 Sep 2017 08:00:24 +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 C71AB24172 for ; Mon, 4 Sep 2017 08:00:23 +0000 (UTC) Date: Mon, 4 Sep 2017 08:00:23 +0000 (UTC) From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28JIRA=29?= To: dev@syncope.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SYNCOPE-1105) Provide unique key for ProvisioningManager operations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 04 Sep 2017 08:00:29 -0000 [ https://issues.apache.org/jira/browse/SYNCOPE-1105?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiricc=C3=B2 updated SYNCOPE-1105: -------------------------------------------- Fix Version/s: (was: 2.0.5) 2.0.6 > Provide unique key for ProvisioningManager operations > ----------------------------------------------------- > > Key: SYNCOPE-1105 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1105 > Project: Syncope > Issue Type: New Feature > Components: console, core > Reporter: Francesco Chicchiricc=C3=B2 > Fix For: 2.0.6, 2.1.0 > > > The operations driven by the ProvisioningManager (e.g. CREATE / UPDATE / = DELETE about User / Group / Any Object entities) do not currently provide a= ny mean to bind together the various activity involved, which generally are= : > # CREATE / UPDATE / DELETE onto the internal storage via WorkflowAdapter > # propagation towards the assigned (direct and via group membership, when= applicable) External Resources > If a unique key is generated for the ongoing operation, such key can be a= lso associated to the audit entries and notification messages (when enabled= ). > This would allow, for example, to expose a new REST endpoint for querying= the Audit table. > Sample use case: trace what happens when creating user via REST with asyn= chronous propagations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)