Bug 991124

Summary: Incorrect user in Task API (SAML-BEARER-TOKEN)
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: kconner
Component: DT GovernanceAssignee: Eric Wittmann <eric.wittmann>
Status: CLOSED CURRENTRELEASE QA Contact: Stefan Bunciak <sbunciak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0 GACC: ldimaggi, soa-p-jira
Target Milestone: ER1   
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 kconner 2013-08-01 16:56:51 UTC 
The Task API implementation is currently pulling the auth user from the request incorrectly. It should be pulling the Principal from the request rather than simply asking for the remote user string. In the case of SAML bearer token authentication the remote user string is wrong. I believe the Principal should be right, however. If it is not, then the security context should be used to retrieve the right principal.
Comment 1 Stefan Bunciak 2013-08-28 09:01:38 UTC 
Verified in S-RAMP 6.0.0.ER1