Hi Santosh, Why are you adding the security header by hand? Didn't you engage rampart on the client side with the required security policy so that rampart will add these security headers for you? Does the WSDL include a policy stating what security measures should be taken to access the service?
Thanks, Keith. On Wed, Jun 18, 2008 at 12:26 PM, sh_santosh <[EMAIL PROTECTED]> wrote: > >> not > Security Header is not present in the incoming message > Exception. > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > X-Nabble-From: [EMAIL PROTECTED] > > > Dear All, > > I have a Java Client generated by using Axis1.3.By use of my Java Client I > want to access a Web Service Implemented in .NET using WSE3.0 Standards. > > When I tried to submit my Request using a method available in my Client > Class ,I am getting Exception that "Security requirements are not satisfied > because the security header is not present in the incoming message". > > Then I have added the SOAP Security Headers(which are not available in my > Java Client Code) in my Stub Object by using SOAPHeaderElement Class's > Object and Tried to submit the Request ,but still I got the Same Exception. > > Note : - That the Java Client Code Pass an Object as Request having > required > Parameters and Gets the User Defined Object in Response. > > I have to generate a Structure Like below inside my SOAPHeader Tag : > > <soap:Header> > <wsa:Action>http://www.test/info</wsa:Action> > > <wsa:MessageID>urn:uuid:ca6e465b-484a-4bb5-964f-eb513938bb84</wsa:MessageID> > <wsa:ReplyTo> > <wsa:Address> > http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous > </wsa:Address> > </wsa:ReplyTo> > <wsa:To>http://localhost:8080/bookingapi/bookingapi.asmx</wsa:To> > <wsse:Security soap:mustUnderstand="1"> > <wsu:Timestamp wsu:Id="Timestamp-c90b72e0-541c-4b17-bc0b-acf8c3495b43"> > <wsu:Created>2008-02-28T15:33:56Z</wsu:Created> > <wsu:Expires>2008-02-28T15:38:56Z</wsu:Expires> > </wsu:Timestamp> > <wsse:UsernameToken > xmlns:wsu=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd > " > wsu:Id="SecurityToken-9e141575-2400-4c6d-ab86-1d5af61727b2"> > <wsse:Username>[EMAIL PROTECTED]</wsse:Username> > <wsse:Password > Type=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText > ">SomePassword</wsse:Password> > <wsse:Nonce>5SImW1gykzSPdeiWzcCdaQ==</wsse:Nonce> > <wsu:Created>2008-02-28T15:33:56Z</wsu:Created> > </wsse:UsernameToken> > </wsse:Security> > </soap:Header> > > > > Any Help at Java Code Level or any Guidance/Example will be highly > appreciated. > > Thanks, > Ritesh. > > -- > View this message in context: > http://www.nabble.com/Security-requirements-are-not-satisfied-because-the-security-header-is%0D%0A%3E%3E-not%0D%0ASecurity-Header-is-not-present-in-the-incoming-message-Exception.-tp17960865p17960865.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
