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 0CF1F200CBB for ; Tue, 4 Jul 2017 13:06:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0B99E160E21; Tue, 4 Jul 2017 11:06:06 +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 5230E160E1F for ; Tue, 4 Jul 2017 13:06:05 +0200 (CEST) Received: (qmail 42349 invoked by uid 500); 4 Jul 2017 11:06:04 -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 42338 invoked by uid 99); 4 Jul 2017 11:06:04 -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; Tue, 04 Jul 2017 11:06:04 +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 E40B7181819 for ; Tue, 4 Jul 2017 11:06:03 +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-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id qkcvHEzWHX1E for ; Tue, 4 Jul 2017 11:06:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 479075FDAD for ; Tue, 4 Jul 2017 11:06: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 67C2AE08C3 for ; Tue, 4 Jul 2017 11:06: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 27D7624606 for ; Tue, 4 Jul 2017 11:06:00 +0000 (UTC) Date: Tue, 4 Jul 2017 11:06:00 +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-1143) Fine-grained administration rights for Connector and Resources MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 04 Jul 2017 11:06:06 -0000 [ https://issues.apache.org/jira/browse/SYNCOPE-1143?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiricc=C3=B2 updated SYNCOPE-1143: -------------------------------------------- Description:=20 The current delegated administration model defines coarse-grained entitleme= nts when it comes to Connectors and Resources: either an administrator can = manage all connectors and / or all resources, or cannot. By associating Connectors (and Resources, by consequence) to Realms, it is = possible to grant entitlements (via Roles) to a given subset of all availab= le Connector and Resources, e.g. the ones associated to specific Realm(s). Samples: * if a Connector has the Realm {{/a/b/c}} assigned, then it would be manag= eable by users owning the {{CONNECTOR_UPDATE}} on Realm {{/a/b/c}} (or one = of its parents) * if a Resource is related to a Connector with the Realm {{/a/b/c}} assign= ed, then it would be manageable by users owning the {{RESOURCE_UPDATE}} on = Realm {{/a/b/c}} (or one of its parents) was: The current delegated administration model defines coarse-grained entitleme= nts when it comes to Connectors and Resources: either an administrator can = manage all connectors and / or all resources, or cannot. By associating Connectors (and Resources, by consequence) to Realms, it is = possible to grant entitlements (via Roles) to a given subset of all availab= le Connector and Resources, e.g. the ones associated to specific Realm(s). > Fine-grained administration rights for Connector and Resources > -------------------------------------------------------------- > > Key: SYNCOPE-1143 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1143 > Project: Syncope > Issue Type: Improvement > Components: common, console, core > Reporter: Francesco Chicchiricc=C3=B2 > Fix For: 2.0.5, 2.1.0 > > > The current delegated administration model defines coarse-grained entitle= ments when it comes to Connectors and Resources: either an administrator ca= n manage all connectors and / or all resources, or cannot. > By associating Connectors (and Resources, by consequence) to Realms, it i= s possible to grant entitlements (via Roles) to a given subset of all avail= able Connector and Resources, e.g. the ones associated to specific Realm(s)= . > Samples: > * if a Connector has the Realm {{/a/b/c}} assigned, then it would be man= ageable by users owning the {{CONNECTOR_UPDATE}} on Realm {{/a/b/c}} (or on= e of its parents) > * if a Resource is related to a Connector with the Realm {{/a/b/c}} assi= gned, then it would be manageable by users owning the {{RESOURCE_UPDATE}} o= n Realm {{/a/b/c}} (or one of its parents) -- This message was sent by Atlassian JIRA (v6.4.14#64029)