Bug 1026698

Summary: Use SecurityContextManager to retrieve context in case sealed
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Gary Brown <gbrown>
Component: RT GovernanceAssignee: Gary Brown <gbrown>
Status: CLOSED CURRENTRELEASE QA Contact: Jiri Pechanec <jpechane>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: ldimaggi, soa-p-jira
Target Milestone: ER7   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gary Brown 2013-11-05 09:30:29 UTC 
Description of problem:

The RTGov activity collector and validator directly accesses the SecurityContext from the properties on the camel exchange. The problem with this approach is if the SecurityContext is sealed.

After discussion with Keith Babo and David Ward, the best approach is to access the SecurityContext using the SecurityContextManager - but this requires the use of the SwitchYard exchange instead of the Camel Exchange.

Therefore two changes are required:

1) Switch to using the switchyard ExchangeInitiatedEvent and ExchangeCompletionEvent, instead of the camel equivalent events. (RTGOV-247)

2) Change the AbstractExchangeValidator be based on the ExchangeInterceptor mechanism instead of Auditor. (RTGOV-311)
Comment 2 Jiri Pechanec 2014-01-07 12:52:11 UTC 
Verified in ER8
Comment 3 JBoss JIRA Server 2014-07-02 09:18:46 UTC 
Gary Brown <gary> updated the status of jira RTGOV-247 to Closed
Comment 4 JBoss JIRA Server 2014-07-02 09:19:15 UTC 
Gary Brown <gary> updated the status of jira RTGOV-311 to Closed