This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 991124 - Incorrect user in Task API (SAML-BEARER-TOKEN)
Incorrect user in Task API (SAML-BEARER-TOKEN)
Status: CLOSED CURRENTRELEASE
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: DT Governance (Show other bugs)
6.0.0 GA
Unspecified Unspecified
unspecified Severity unspecified
: ER1
: 6.0.0
Assigned To: Eric Wittmann
Stefan Bunciak
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-01 12:56 EDT by kconner
Modified: 2014-02-06 10:33 EST (History)
2 users (show)

See Also:
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: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker DTGOV-44 Major Closed Incorrect user in Task API (SAML-BEARER-TOKEN) 2013-08-28 05:01:44 EDT

  None (edit)
Description kconner 2013-08-01 12:56:51 EDT
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 05:01:38 EDT
Verified in S-RAMP 6.0.0.ER1

Note You need to log in before you can comment on or make changes to this bug.