Return-Path: <dev-return-54575-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 61761200B8E
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon, 26 Sep 2016 20:27:22 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 5FCD2160ACA; Mon, 26 Sep 2016 18:27:22 +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 A3F7A160AC8
	for <archive-asf-public@cust-asf.ponee.io>; Mon, 26 Sep 2016 20:27:21 +0200 (CEST)
Received: (qmail 96581 invoked by uid 500); 26 Sep 2016 18:27:20 -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 96568 invoked by uid 99); 26 Sep 2016 18:27:20 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Sep 2016 18:27:20 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 928862C2A5F
	for <dev@directory.apache.org>; Mon, 26 Sep 2016 18:27:20 +0000 (UTC)
Date: Mon, 26 Sep 2016 18:27:20 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.12935281.1454106493000.666119.1474914440597@Atlassian.JIRA>
In-Reply-To: <JIRA.12935281.1454106493000@Atlassian.JIRA>
References: <JIRA.12935281.1454106493000@Atlassian.JIRA> <JIRA.12935281.1454106493348@arcas>
Subject: [jira] [Commented] (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: Mon, 26 Sep 2016 18:27:22 -0000


    [ https://issues.apache.org/jira/browse/FC-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15523822#comment-15523822 ] 

ASF GitHub Bot commented on FC-144:
-----------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/directory-fortress-enmasse/pull/1


> 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.1
>            Reporter: Florin Stingaciu
>            Assignee: Vyacheslav Vakhlyuev
>             Fix For: 1.0.2
>
>
> 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)