You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Gina Choi <gi...@gmail.com> on 2012/07/16 13:35:31 UTC
Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP 1.1
only endpoint
Hi All,
One of my colleage sent a SOAP1.2 RST to Fediz STS UTEncrypted end point
from his .NET client and he received back following response. He changed
format to SOAP1.1 to get by this error message, but he really need to run
with SOAP1.2. Is there anywhere to enable SOAP1.2 message in STS to accept
1.2 format?
<MessageLogTraceRecord>
<HttpResponse xmlns="*
http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace*">
<StatusCode>*InternalServerError*</StatusCode>
<StatusDescription>*Internal Server Error*</StatusDescription>
<WebHeaders>
<Transfer-Encoding>*chunked*</Transfer-Encoding>
<Connection>*close*</Connection>
<Content-Type>*application/soap+xml;charset=UTF-8*</Content-Type>
<Date>*Wed, 11 Jul 2012 12:34:20 GMT*</Date>
<Server>*Apache-Coyote/1.1*</Server>
</WebHeaders>
</HttpResponse>
<soap:Envelope xmlns:soap="*http://www.w3.org/2003/05/soap-envelope*">
<s:Header xmlns:s="*http://www.w3.org/2003/05/soap-envelope*"></s:Header>
<soap:Body>
<soap:Fault>
<faultcode xmlns:ns1="*http://schemas.xmlsoap.org/soap/envelope/*" xmlns="">
*ns1:VersionMismatch*</faultcode>
<faultstring xmlns="">*A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint.*</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
</MessageLogTraceRecord>
Thanks.
Gina
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Colm O hEigeartaigh <co...@apache.org>.
> Is there anywhere to enable SOAP1.2 message in STS to accept 1.2 format?
You need to add an endpoint to the STS WSDL that uses a SOAP 1.2 binding.
Colm.
On Mon, Jul 16, 2012 at 12:35 PM, Gina Choi <gi...@gmail.com> wrote:
> Hi All,
>
> One of my colleage sent a SOAP1.2 RST to Fediz STS UTEncrypted end point
> from his .NET client and he received back following response. He changed
> format to SOAP1.1 to get by this error message, but he really need to run
> with SOAP1.2. Is there anywhere to enable SOAP1.2 message in STS to accept
> 1.2 format?
>
>
> <MessageLogTraceRecord>
>
> <HttpResponse xmlns="*
> http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace*
> ">
>
> <StatusCode>*InternalServerError*</StatusCode>
>
> <StatusDescription>*Internal Server Error*</StatusDescription>
>
> <WebHeaders>
>
> <Transfer-Encoding>*chunked*</Transfer-Encoding>
>
> <Connection>*close*</Connection>
>
> <Content-Type>*application/soap+xml;charset=UTF-8*</Content-Type>
>
> <Date>*Wed, 11 Jul 2012 12:34:20 GMT*</Date>
>
> <Server>*Apache-Coyote/1.1*</Server>
>
> </WebHeaders>
>
> </HttpResponse>
>
> <soap:Envelope xmlns:soap="*http://www.w3.org/2003/05/soap-envelope*">
>
> <s:Header xmlns:s="*http://www.w3.org/2003/05/soap-envelope*"></s:Header>
>
> <soap:Body>
>
> <soap:Fault>
>
> <faultcode xmlns:ns1="*http://schemas.xmlsoap.org/soap/envelope/*"
> xmlns="">
> *ns1:VersionMismatch*</faultcode>
>
> <faultstring xmlns="">*A SOAP 1.2 message is not valid when sent to a SOAP
> 1.1 only endpoint.*</faultstring>
>
> </soap:Fault>
>
> </soap:Body>
>
> </soap:Envelope>
>
> </MessageLogTraceRecord>
>
>
> Thanks.
>
> Gina
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Glen Mazza <gm...@talend.com>.
It could work as-is but IIRC you'll need to regenerate your WSDL-to-Java
artifacts with the updated WSDL that hits the SOAP 1.2 endpoint, as
there's changes to the Service and/or Port classes indicating a SOAP 1.2
endpoint is being accessed.
Glen
On 07/16/2012 09:50 AM, Gina Choi wrote:
> Glen:
> <<<
> I ran the CXF STS on SOAP 1.2 endpoints before when testing
> interoperability with Metro. It should work, the WSDL will just need some
> modifications (http://www.jroller.com/gmazza/entry/switch_soap11_to_soap12).
>>>> >>>
> I changed wsdl file from 1.1 to 1.2 based on your tutorial in the past. My
> Java client to Fediz STS is fine with 1.1. If I change wsdl file to 1.2, my
> CXF client will be automatically generate 1.2 message to communicate with
> 1.2 end point?
>
> Thanks.
>
> Gina
>
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Gina Choi <gi...@gmail.com>.
I converted my STS wsdl file to 1.2 format based on Glen Mazza's web
tutorial(http://www.jroller.com/gmazza/entry/switch_soap11_to_soap12) in
case someone want to do same thing. I used NotePad String replace and
finished it in 2 min.
Thanks.
Gina
On Tue, Jul 17, 2012 at 10:12 AM, Gina Choi <gi...@gmail.com> wrote:
> Hi Oliver,
>
> I opened a ticket in JIRA as an improvement request.
> https://issues.apache.org/jira/browse/FEDIZ-17
>
> Thanks.
>
> Gina
>
>
> On Tue, Jul 17, 2012 at 1:47 AM, Oliver Wulff <ow...@talend.com> wrote:
>
>> Hi Gina
>>
>> Can you please raise a JIRA?
>>
>> Thanks
>> Oli
>>
>>
>> ------
>>
>> Oliver Wulff
>>
>> Blog: http://owulff.blogspot.com
>> Solution Architect
>> http://coders.talend.com
>>
>> Talend Application Integration Division http://www.talend.com
>>
>
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Gina Choi <gi...@gmail.com>.
Hi Oliver,
I opened a ticket in JIRA as an improvement request.
https://issues.apache.org/jira/browse/FEDIZ-17
Thanks.
Gina
On Tue, Jul 17, 2012 at 1:47 AM, Oliver Wulff <ow...@talend.com> wrote:
> Hi Gina
>
> Can you please raise a JIRA?
>
> Thanks
> Oli
>
>
> ------
>
> Oliver Wulff
>
> Blog: http://owulff.blogspot.com
> Solution Architect
> http://coders.talend.com
>
> Talend Application Integration Division http://www.talend.com
>
RE: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Oliver Wulff <ow...@talend.com>.
Hi Gina
Can you please raise a JIRA?
Thanks
Oli
------
Oliver Wulff
Blog: http://owulff.blogspot.com
Solution Architect
http://coders.talend.com
Talend Application Integration Division http://www.talend.com
________________________________________
From: Daniel Kulp [dkulp@apache.org]
Sent: 16 July 2012 17:00
To: Gina Choi
Cc: users@cxf.apache.org
Subject: Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint
On Monday, July 16, 2012 10:54:26 AM Gina Choi wrote:
> <<<
> Note that with CXF, a 1.2 endpoint will also handle 1.1 requests just
> fine. The 1.2 endpoint will detect a 1.1 request and respond with the
> appropriate 1.1 based response. Thus, you just need to deploy a 1.2
> endpoint and it should be able to handle both types of clients fine.
>
> Thanks Dan. I will do that.
>
> If that case, shouldn't we make all Fediz STS end points 1.2 as default(I
> mean Fediz STS release version), so that users do not need to go through
> conversion work?
It's definitely not a BAD suggestion. :-)
For the WS-N stuff, that's exactly what I did. When using CXF, it is now
exposed via SOAP 1.2.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint
Posted by Daniel Kulp <dk...@apache.org>.
On Monday, July 16, 2012 10:54:26 AM Gina Choi wrote:
> <<<
> Note that with CXF, a 1.2 endpoint will also handle 1.1 requests just
> fine. The 1.2 endpoint will detect a 1.1 request and respond with the
> appropriate 1.1 based response. Thus, you just need to deploy a 1.2
> endpoint and it should be able to handle both types of clients fine.
>
> Thanks Dan. I will do that.
>
> If that case, shouldn't we make all Fediz STS end points 1.2 as default(I
> mean Fediz STS release version), so that users do not need to go through
> conversion work?
It's definitely not a BAD suggestion. :-)
For the WS-N stuff, that's exactly what I did. When using CXF, it is now
exposed via SOAP 1.2.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Gina Choi <gi...@gmail.com>.
<<<
Note that with CXF, a 1.2 endpoint will also handle 1.1 requests just fine.
The 1.2 endpoint will detect a 1.1 request and respond with the appropriate
1.1 based response. Thus, you just need to deploy a 1.2 endpoint and it
should be able to handle both types of clients fine.
>>>
Thanks Dan. I will do that.
If that case, shouldn't we make all Fediz STS end points 1.2 as default(I
mean Fediz STS release version), so that users do not need to go through
conversion work?
Gina
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint
Posted by Daniel Kulp <dk...@apache.org>.
On Monday, July 16, 2012 09:50:40 AM Gina Choi wrote:
> Colm and Glen,
>
> Thanks for your responses. I think that you two suggest two different
> solutions. One is supporting both 1.1 and 1.2 and the other is supporting
> solely 1.2.
Note that with CXF, a 1.2 endpoint will also handle 1.1 requests just fine.
The 1.2 endpoint will detect a 1.1 request and respond with the appropriate
1.1 based response. Thus, you just need to deploy a 1.2 endpoint and it
should be able to handle both types of clients fine.
Dan
>
> Colm:
> <<<
> You need to add an endpoint to the STS WSDL that uses a SOAP 1.2 binding.
>
> So, I need to add another endpoint in ws-trust-1.4-service.wsdl file like
> bellow? Do I need to create UTEncrypted_Binding in similar way?
>
> <wsdl:service name="SecurityTokenService">
>
> <wsdl:port name="UTEncrypted_Port"
> binding="tns:UTEncrypted_Binding">
>
> <soap:address location="http://localhost:8080/jaxws-sts/sts" />
>
> </wsdl:port>
>
> <wsdl:port name="UTEncrypted_Port12"
> binding="tns:UTEncrypted_Binding">
>
> <soap12:address location="http://localhost:8080/jaxws-sts/sts" />
>
> </wsdl:port>
>
>
> Glen:
> <<<
> I ran the CXF STS on SOAP 1.2 endpoints before when testing
> interoperability with Metro. It should work, the WSDL will just need some
> modifications
> (http://www.jroller.com/gmazza/entry/switch_soap11_to_soap12).
>
> I changed wsdl file from 1.1 to 1.2 based on your tutorial in the past. My
> Java client to Fediz STS is fine with 1.1. If I change wsdl file to 1.2,
> my CXF client will be automatically generate 1.2 message to communicate
> with 1.2 end point?
>
> Thanks.
>
> Gina
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Gina Choi <gi...@gmail.com>.
Colm and Glen,
Thanks for your responses. I think that you two suggest two different
solutions. One is supporting both 1.1 and 1.2 and the other is supporting
solely 1.2.
Colm:
<<<
You need to add an endpoint to the STS WSDL that uses a SOAP 1.2 binding.
>>>
So, I need to add another endpoint in ws-trust-1.4-service.wsdl file like
bellow? Do I need to create UTEncrypted_Binding in similar way?
<wsdl:service name="SecurityTokenService">
<wsdl:port name="UTEncrypted_Port" binding="tns:UTEncrypted_Binding">
<soap:address location="http://localhost:8080/jaxws-sts/sts" />
</wsdl:port>
<wsdl:port name="UTEncrypted_Port12"
binding="tns:UTEncrypted_Binding">
<soap12:address location="http://localhost:8080/jaxws-sts/sts" />
</wsdl:port>
Glen:
<<<
I ran the CXF STS on SOAP 1.2 endpoints before when testing
interoperability with Metro. It should work, the WSDL will just need some
modifications (http://www.jroller.com/gmazza/entry/switch_soap11_to_soap12).
>>>
I changed wsdl file from 1.1 to 1.2 based on your tutorial in the past. My
Java client to Fediz STS is fine with 1.1. If I change wsdl file to 1.2, my
CXF client will be automatically generate 1.2 message to communicate with
1.2 end point?
Thanks.
Gina
Re: Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint
Posted by Glen Mazza <gm...@talend.com>.
I ran the CXF STS on SOAP 1.2 endpoints before when testing
interoperability with Metro. It should work, the WSDL will just need
some modifications
(http://www.jroller.com/gmazza/entry/switch_soap11_to_soap12).
Glen
On 07/16/2012 07:35 AM, Gina Choi wrote:
> Hi All,
>
> One of my colleage sent a SOAP1.2 RST to Fediz STS UTEncrypted end point
> from his .NET client and he received back following response. He changed
> format to SOAP1.1 to get by this error message, but he really need to run
> with SOAP1.2. Is there anywhere to enable SOAP1.2 message in STS to accept
> 1.2 format?
>
>
> <MessageLogTraceRecord>
>
> <HttpResponse xmlns="*
> http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace*">
>
> <StatusCode>*InternalServerError*</StatusCode>
>
> <StatusDescription>*Internal Server Error*</StatusDescription>
>
> <WebHeaders>
>
> <Transfer-Encoding>*chunked*</Transfer-Encoding>
>
> <Connection>*close*</Connection>
>
> <Content-Type>*application/soap+xml;charset=UTF-8*</Content-Type>
>
> <Date>*Wed, 11 Jul 2012 12:34:20 GMT*</Date>
>
> <Server>*Apache-Coyote/1.1*</Server>
>
> </WebHeaders>
>
> </HttpResponse>
>
> <soap:Envelope xmlns:soap="*http://www.w3.org/2003/05/soap-envelope*">
>
> <s:Header xmlns:s="*http://www.w3.org/2003/05/soap-envelope*"></s:Header>
>
> <soap:Body>
>
> <soap:Fault>
>
> <faultcode xmlns:ns1="*http://schemas.xmlsoap.org/soap/envelope/*" xmlns="">
> *ns1:VersionMismatch*</faultcode>
>
> <faultstring xmlns="">*A SOAP 1.2 message is not valid when sent to a SOAP
> 1.1 only endpoint.*</faultstring>
>
> </soap:Fault>
>
> </soap:Body>
>
> </soap:Envelope>
>
> </MessageLogTraceRecord>
>
>
> Thanks.
>
> Gina
>
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza