[
https://issues.apache.org/jira/browse/RAMPART-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagara Gunathunga moved AXIS2-5290 to RAMPART-370:
---------------------------------------------------
Fix Version/s: (was: 1.6.3)
1.6.3
Component/s: (was: jaxws)
Affects Version/s: (was: 1.6.0)
1.6.0
Key: RAMPART-370 (was: AXIS2-5290)
Project: Rampart (was: Axis2)
> Interoperability issue between Axis2 and secured (WSS) webservice hosted in
> Weblogic
> -------------------------------------------------------------------------------------
>
> Key: RAMPART-370
> URL: https://issues.apache.org/jira/browse/RAMPART-370
> Project: Rampart
> Issue Type: Bug
> Affects Versions: 1.6.0
> Environment: I have a JAX-WS webservice hosted in Weblogic which is
> protected by a X509 token policy and I have tried to have an adb (standard)
> Axis2 client which will be able to communicate with it.
> Reporter: François Courtault
> Fix For: 1.6.3
>
> Attachments: Axis X509 SOAP request
> (Wssp1.2-2007-Wss1.1-X509-Basic256) which doesn't work.txt.zip, SOAP request
> (Wssp1.2-2007-Wss1.1-X509-Basic256) which works.txt.zip,
> Wssp1.2-2007-Wss1.1-X509-Basic256.xml
>
>
> In fact I was not able to have an axis2 client which works with this
> webservice hosted in Weblogic.
> If I compare the Axis2 request which doesn't work with an SOAP request which
> works it seems that a section is missing <wsse:KeyIdentifier> inside the
> <ds:KeyInfo...> <<wsse:SecurityTokenReference ...>
> Just for your information, CXF 2.5.2 has the same issue
> (https://issues.apache.org/jira/browse/CXF-4166) and they provide me a fix.
> Could please do the same ?
> Regards.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
