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.
Darran Lofthouse <darran.lofthouse> updated the status of jira WFLY-2044 to Coding In Progress
Verified with EAP 6.2.0.ER7.