Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Date: Mon, 28 May 2012 10:59:23 +0000 (UTC)
From: =?utf-8?Q?Fran=C3=A7ois_Courtault_=28JIRA=29?= <jira@apache.org>
To: java-dev@axis.apache.org
Message-ID: <1464651577.8372.1338202763570.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1926106791.7806.1334071158654.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (RAMPART-370) Interoperability issue between
 Axis2 and secured (WSS)  webservice hosted in Weblogic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/RAMPART-370?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D132=
84367#comment-13284367 ]=20

Fran=C3=A7ois Courtault commented on RAMPART-370:
--------------------------------------------

Hello,

I have updated this issue because it is a show stopper for us.

Just one remark, I haven't seen so much activity on this issue since my fir=
st post :-(

Best Regards.
               =20
> 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 (standa=
rd) Axis2 client which will be able to communicate with it.
>            Reporter: Fran=C3=A7ois Courtault
>            Priority: Blocker
>             Fix For: 1.6.3
>
>         Attachments: Axis X509 SOAP request (Wssp1.2-2007-Wss1.1-X509-Bas=
ic256) 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 webs=
ervice hosted in Weblogic.
> If I compare the Axis2 request which doesn't work with an SOAP request wh=
ich works it seems that a section is missing <wsse:KeyIdentifier> inside th=
e <ds:KeyInfo...> <<wsse:SecurityTokenReference ...>
> Just for your information, CXF 2.5.2 has the same issue (https://issues.a=
pache.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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org