Return-Path: <dev-return-54443-archive-asf-public=cust-asf.ponee.io@directory.apache.org>
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 53643200B79
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 23 Aug 2016 14:12:23 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 521F9160AA5; Tue, 23 Aug 2016 12:12:23 +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 A1457160AAD
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 23 Aug 2016 14:12:22 +0200 (CEST)
Received: (qmail 86054 invoked by uid 500); 23 Aug 2016 12:12:21 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 85803 invoked by uid 99); 23 Aug 2016 12:12:21 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2016 12:12:21 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 852572C0154
	for <dev@directory.apache.org>; Tue, 23 Aug 2016 12:12:21 +0000 (UTC)
Date: Tue, 23 Aug 2016 12:12:21 +0000 (UTC)
From: "Shawn McKinney (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12935281.1454106493000.382664.1471954341543@Atlassian.JIRA>
In-Reply-To: <JIRA.12935281.1454106493000@Atlassian.JIRA>
References: <JIRA.12935281.1454106493000@Atlassian.JIRA> <JIRA.12935281.1454106493348@arcas>
Subject: [jira] [Updated] (FC-144) Ability to assign groups to roles
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 23 Aug 2016 12:12:23 -0000


     [ https://issues.apache.org/jira/browse/FC-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shawn McKinney updated FC-144:
------------------------------
    Assignee: Vyacheslav Vakhlyuev

> Ability to assign groups to roles
> ---------------------------------
>
>                 Key: FC-144
>                 URL: https://issues.apache.org/jira/browse/FC-144
>             Project: FORTRESS
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-RC40
>            Reporter: Florin Stingaciu
>            Assignee: Vyacheslav Vakhlyuev
>
> We are currently working on performing an integration between Openstack Keystone and Fortress Core. We will use Fortress as the authorization backend for the rest of Openstack. We have managed to map most of the current functionality in Openstack within the Fortress schema except for the ability to assign roles to a group. 
> I've spoken with [~smckinney], and he determined this improvement is a feasible addition to Fortress's feature set. After a number of back and forths, we have come up with the following requirements as API additions:
> * Session createSession (Group group, boolean isTrusted);
> * void assignGroup ( Group group, Role role );
> * List<Group> roleGroups ( Role role );
> * List<Role> groupRoles ( Group group );
> * the ability to use the above session with checkAccess(Session session, Permission perm)
> We also discussed temporal constrains for group to role assignment. Temporal constrains will not be utilized as this functionality has not been defined in Openstack.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)