Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Date: Wed, 12 Oct 2016 12:49:20 +0000 (UTC)
From: "Chris Pike (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Message-ID: <JIRA.13011656.1476276518000.804479.1476276560426@Atlassian.JIRA>
In-Reply-To: <JIRA.13011656.1476276518000@Atlassian.JIRA>
References: <JIRA.13011656.1476276518000@Atlassian.JIRA> <JIRA.13011656.1476276518844@arcas>
Subject: [jira] [Created] (FC-195) ARBAC Role Grouping
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 12 Oct 2016 12:49:22 -0000

Chris Pike created FC-195:
-----------------------------

             Summary: ARBAC Role Grouping
                 Key: FC-195
                 URL: https://issues.apache.org/jira/browse/FC-195
             Project: FORTRESS
          Issue Type: Improvement
            Reporter: Chris Pike
            Assignee: Chris Pike


User Story: As a fortress super administrator, I want to delegate Role Management (Creation and Permission Assignment) to application owners

Current Steps:
 1. Create an ARBAC Role (AR1) that has jurisdiction over Perm OU (POU1) and Role Range (RR1)
 2. Assign User (U1) into AR1
 3. U1 creates new Role (R1)
 4. U1 adds Permission (P1) into R1 but is denied since R1 doesn't belong to RR1

Steps After ARBAC Role Group
 1. Create an ARBAC Role (AR1) that has jurisdiction over Perm OU (POU1) and Role Group (RG1)
 2. Assign User (U1) into AR1
 3. U1 creates new Role (R1) with Group of RG1
 4. U1 adds Permission (P1) into R1


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