Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1121223 - [GSS] (6.4.0) [CXF-5892] Ensure EncryptedKey references BinarySecurityToken before it
[GSS] (6.4.0) [CXF-5892] Ensure EncryptedKey references BinarySecurityToken b...
Status: VERIFIED
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services (Show other bugs)
6.3.0
Unspecified Unspecified
urgent Severity unspecified
: DR10
: EAP 6.4.0
Assigned To: Alessio Soldano
Rostislav Svoboda
:
Depends On:
Blocks: 1115213 1121227 1153972
  Show dependency treegraph
 
Reported: 2014-07-18 12:51 EDT by Kyle Lape
Modified: 2018-03-06 15:38 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous releases of JBoss EAP 6, CXF placed the `BinarySecurityToken` referenced by the EncryptedKey element after the EncryptedKey element when the WSS timestamp was not included in the SOAP message. This could cause receivers that expect the `BinarySecurityToken` referenced by the EncryptedKey to be above the EncryptedKey element to fail as they had not processed the `BinarySecurityToken` when attempting to look it up while processing the EncryptedKey element. This issue has been resolved by moving the BinarySecurityToken higher in the SOAP message. Now `EncryptedKey` elements always reference `BinarySecurityTokens` that have already been found while parsing the SOAP message.
Story Points: ---
Clone Of: 1115215
: 1121227 (view as bug list)
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
Apache JIRA CXF-5892 None None None Never

  None (edit)
Comment 7 Kabir Khan 2014-11-10 13:32:19 EST
See component upgrade https://bugzilla.redhat.com/show_bug.cgi?id=1153972#c2 for explanation of why the upgrade was reverted and this BZ is set back to ASSIGNED
Comment 8 Jan Blizňák 2014-11-18 07:42:00 EST
Verified on 6.4.0.DR10

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