Bug 1007514 - Update the installer for access control / RBAC
Summary: Update the installer for access control / RBAC
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Thomas Hauser
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-12 16:04 UTC by Darran Lofthouse
Modified: 2017-10-10 00:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 14:34:26 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Darran Lofthouse 2013-09-12 16:04:51 UTC 
Description of problem:

Now that EAP 6.2 is having access control made available the installer may require updates to simplify enabling it.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Thomas Hauser 2013-09-12 17:17:33 UTC 
Please link some documentation (preferably with related jboss-cli commands, or requisite xml changes) so we can evaluate the impact / ease of getting this into the installer for 6.2.0! :)
Comment 2 Darran Lofthouse 2014-05-07 18:13:40 UTC 
Do we have any links to the docs for access control that Thomas can make use of?
Comment 3 Petr Kremensky 2014-05-14 07:33:12 UTC 
We could update the User panel giving user an option to choose between simple (user + password) and RBAC authorization (just an idea), however I think its too late now for 6.3.0 now.

http://documentation-devel.engineering.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html-single/Security_Guide/index.html#sect-Configuring_Role-Based_Access_Control
Comment 4 Thomas Hauser 2014-07-04 14:34:26 UTC 
Agreed with Petr above. Too late for 6.3.0.
Note You need to log in before you can comment on or make changes to this bug.