[
https://issues.jboss.org/browse/GTNWSRP-288?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration commented on GTNWSRP-288:
-------------------------------------------------
Jared MORGAN <jmorgan(a)redhat.com> made a comment on [bug
829885|https://bugzilla.redhat.com/show_bug.cgi?id=829885]
Technical note updated. If any revisions are required, please edit the "Technical
Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services
team.
Diffed Contents:
@@ -1,4 +1 @@
-Cause: JBossWS supports X.509 token with WSSE.
+It was discovered that JBossWS supports X.509 token with WSSE, however the functionality
only partially worked. It was not possible to encrypt the entire message. The fix
introduces improvements to this aspect of JBossWS in WSRP, and corrects the
issue.-Consequences: Works only partially, encrypt all the message is not possible.
-Fix: Fixed in newer version of WSRP, component updated.
-Result: Encryption work for all messages.
Can't use encryption with ws-security
-------------------------------------
Key: GTNWSRP-288
URL:
https://issues.jboss.org/browse/GTNWSRP-288
Project: GateIn WSRP
Issue Type: Bug
Affects Versions: 2.1.5-GA, 2.2.0-Beta01
Reporter: Matt Wringe
Assignee: Chris Laprun
Fix For: 2.1.7-GA, 2.2.0-Beta03
The encryption ws-security options with GateIn do not currently work properly. You can
add usernames and passwords through ws-security, but errors will occur if you try and use
the encryption options for ws-security.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira