Bug 1022993 - RBAC Subject handling and propagation optimisations.
Summary: RBAC Subject handling and propagation optimisations.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER7
: EAP 6.2.0
Assignee: Darran Lofthouse
QA Contact: Ladislav Thon
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-24 12:17 UTC by Darran Lofthouse
Modified: 2013-12-15 16:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-15 16:19:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-1852 0 Major Resolved Populate the Subject with the required prinicpals for rbac/audit logging earlier 2013-11-08 15:33:36 UTC
Red Hat Issue Tracker WFLY-2044 0 Major Resolved Rework Subject propagation to avoid marshaling. 2013-11-08 15:33:37 UTC
Red Hat Issue Tracker WFLY-2337 0 Major Resolved Eliminate additional round trip exchange of Subject from host controller to app server or slave host controllers. 2013-11-08 15:33:37 UTC

Description Darran Lofthouse 2013-10-24 12:17:48 UTC 
Description of problem:

This issue is to incorporate a number of optimisations related to how the Subject used for access control and audit logging is created and how it is propagated: -
 - Ensure the Subject is created in the call as soon as possible eliminating a need to copy / clone it.
 - Send the Subject direct to server instances and slave host controllers where supported rather than waiting for them to ask for it.
 - Describe the Subject within the protocol rather than marshalling it.
Comment 1 JBoss JIRA Server 2013-10-24 19:04:31 UTC 
Darran Lofthouse <darran.lofthouse> updated the status of jira WFLY-2044 to Coding In Progress
Comment 4 Ladislav Thon 2013-11-06 11:58:20 UTC 
Verified with EAP 6.2.0.ER7.
Note You need to log in before you can comment on or make changes to this bug.