ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker vs. Web Service with WS-Policy

Post new topic  Reply to topic
 Broker vs. Web Service with WS-Policy « View previous topic :: View next topic » 
Author Message
mansante
PostPosted: Tue Feb 07, 2012 7:48 am    Post subject: Broker vs. Web Service with WS-Policy Reply with quote

Newbie

Joined: 07 Feb 2012
Posts: 3
Hi,

I have the following problem when trying to consume (SOAP Request node) of a web service with WS-Policy:

Quote:
CWWSS5555E: The mustUnderstand attribute on the Security header does not have the required value: existing value=null, required value=true


Has anyone experienced this problem?

Thanks!
Back to top
View user's profile Send private message
mansante
PostPosted: Tue Feb 07, 2012 7:50 am    Post subject: Broker vs. Web Service with WS-Policy Reply with quote

Newbie

Joined: 07 Feb 2012
Posts: 3
WSDL, REQUEST, RESPONSE, of de web service!


WSDL
Code:
<definitions xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
             xmlns:wsp="http://www.w3.org/ns/ws-policy"
          xmlns:wsp1_2="http://schemas.xmlsoap.org/ws/2004/09/policy"
          xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns:tns="http://services.mycompany.com/xpto/v1"
          xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://services.mycompany.com/xpto/v1" name="xptoxxx">

<wsp:Policy xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" wsu:Id="xptoxxxPortBinding">
   
   <sp:SignedEncryptedSupportingTokens>
      <wsp:Policy>
         <sp:UsernameToken sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/IncludeToken/AlwaysToRecipient">
            <wsp:Policy>
               <sp:WssUsernameToken10 />
            </wsp:Policy>
         </sp:UsernameToken>
      </wsp:Policy>
   </sp:SignedEncryptedSupportingTokens>
   
   <sp:TransportBinding>
      <wsp:Policy>
         <sp:AlgorithmSuite>
            <wsp:Policy>
               <sp:Basic128 />
            </wsp:Policy>
      </sp:AlgorithmSuite>
      <sp:IncludeTimestamp />
      <sp:Layout>
         <wsp:Policy>
            <sp:Lax />
         </wsp:Policy>
      </sp:Layout>
      <sp:TransportToken>
         <wsp:Policy>
           <sp:HttpsToken RequireClientCertificate="false" />
          </wsp:Policy>
          </sp:TransportToken>
      </wsp:Policy>
   </sp:TransportBinding>
   <sp:Wss10 />
   <wsam:Addressing />
</wsp:Policy>

<types>
<xsd:schema>
<xsd:import namespace="http://services.mycompany.com/xpto/v1" schemaLocation="https://serverX:443/app-xpto-ws-web/xptoxxx?xsd=1" />
</xsd:schema>
<xsd:schema>
<xsd:import namespace="http://services.mycompany.com/EBO/v1" schemaLocation="https://serverX:443/app-xpto-ws-web/xptoxxx?xsd=2" />
</xsd:schema>
</types>
<message name="find">
<part name="parameters" element="tns:find" />
</message>
<message name="findResponse">
<part name="parameters" element="tns:findResponse" />
</message>
<message name="SecException">
<part name="fault" element="tns:SecException" />
</message>
<message name="SysException">
<part name="fault" element="tns:SysException" />
</message>
<message name="BusException">
<part name="fault" element="tns:BusException" />
</message>
<portType name="xptoxxx">
<operation name="find">
<input wsam:Action="http://services.mycompany.com/xpto/v1/xptoxxx/findRequest" message="tns:find" />
<output wsam:Action="http://services.mycompany.com/xpto/v1/xptoxxx/findResponse" message="tns:findResponse" />
<fault message="tns:SecException" name="SecException" wsam:Action="http://services.mycompany.com/xpto/v1/xptoxxx/find/Fault/SecException" />
<fault message="tns:SysException" name="SysException" wsam:Action="http://services.mycompany.com/xpto/v1/xptoxxx/find/Fault/SysException" />
<fault message="tns:BusException" name="SysinessException" wsam:Action="http://services.mycompany.com/xpto/v1/xptoxxx/find/Fault/BusException" />
</operation>
</portType>
<binding name="xptoxxxPortBinding" type="tns:xptoxxx">
<wsp:PolicyReference URI="#xptoxxxPortBinding" />
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<operation name="find">
<soap:operation soapAction="" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
<fault name="SecException">
<soap:fault name="SecException" use="literal" />
</fault>
<fault name="SysException">
<soap:fault name="SysException" use="literal" />
</fault>
<fault name="BusException">
<soap:fault name="SysinessException" use="literal" />
</fault>
</operation>
</binding>
<service name="xptoxxx">
<port name="xptoxxxPort" binding="tns:xptoxxxPortBinding">
<soap:address location="https://serverX:443/app-xpto-ws-web/xptoxxx" />
</port>
</service>
</definitions>




REQUEST
Code:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://services.mycompany.com/xpto/v1">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken wsu:Id="UsernameToken-29" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wsse:Username>USERFAKE</wsse:Username>
<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PASSFAKE</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
   <wsa:Action>http://services.mycompany.com/xpto/v1/xptoxxx/findRequest</wsa:Action>
   <wsa:MessageID>uuid:848d2fbe-821a-4906-b52b-6839f32ccb69</wsa:MessageID>
</soapenv:Header>

   <soapenv:Body>
      <v1:find>
         <arg0>
            <xpto>12345</xpto>
            <xpto1>n</xpto1>
            <xpto2>n</xpto2>
         </arg0>
      </v1:find>
   </soapenv:Body>
</soapenv:Envelope>



RESPONSE
Code:
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema">
   <S:Header>
      <To xmlns="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/08/addressing/anonymous</To>
      <Action S:mustUnderstand="1" xmlns="http://www.w3.org/2005/08/addressing">http://services.mycompany.com/xpto/v1/xptoxxx/findResponse</Action>
      <MessageID xmlns="http://www.w3.org/2005/08/addressing">uuid:18d16f83-07d5-456e-917d-f8f0aae8b2fb</MessageID>
      <RelatesTo xmlns="http://www.w3.org/2005/08/addressing">uuid:769067fb-e14b-4d33-b8c4-470de214d057</RelatesTo>
      <wsse:Security S:mustUnderstand="1">
         <wsu:Timestamp wsu:Id="_1" xmlns:ns15="http://schemas.xmlsoap.org/ws/2006/02/addressingidentity" xmlns:ns14="http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512" xmlns:ns13="http://www.w3.org/2003/05/soap-envelope">
            <wsu:Created>2012-02-03T14:43:41Z</wsu:Created>
            <wsu:Expires>2012-02-03T14:48:41Z</wsu:Expires>
         </wsu:Timestamp>
      </wsse:Security>
   </S:Header>
   <S:Body>
      <ns2:findResponse xmlns:ns2="http://services.mycompany.com/xpto/v1" xmlns:ns3="http://services.mycompany.com/EBO/v1">
         <return>
            <ns3:xpto>1234</ns3:xpto>
            <ns3:xpto1>2</ns3:xpto1>
            <ns3:xpto2>XX XXXXX XXX XXX</ns3:xpto2>
            <ns3:xpto3>XXXX XX</ns3:xpto3>
            <ns3:xpto4>XXXXXX XXXX XXXXX XXX</ns3:xpto4>
         </return>
      </ns2:findResponse>
   </S:Body>
</S:Envelope>


Last edited by mansante on Tue Feb 07, 2012 7:51 am; edited 1 time in total
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Tue Feb 07, 2012 7:50 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
You need to set up your WMB runtime to support WS-Security.

If you are novice, you need to contract a qualified WMB consultant to do it.

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.wmb_v6/wmb/6.1/WebServices/WMB61_IEA_WebServices_WS_Security/player.html
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Broker vs. Web Service with WS-Policy
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.