Hi Jose,

Thanks for your reply,

Problem with my Java Client Code is that I have a Limitation that either I
can add Security headers to my org.apache.axis.client.Call class object or
in the Stub class object.

Can you guide me about, how I can use WSS4J classes and method with my Call
or Stub's Class Object.so that i can set the security headers.

Can you provide me some sample Java code or example ,from where I can get
the idea that how should go further ,because right now I am totally stucked
because of this.

Thanks,
Ritesh.



José Ferreiro wrote:
> 
> Hello Ritesh,
> 
> If you are using Axis 1.x (i.e Axis 1.1, 1.2, 1.3 or 1.4) [1] then you
> should use
> the library Apache WSS4J [2] and not "Rampart"
> 
> "Rampart" is a module based on Apache WSS4J that provides the WS-Security
> features for Axis2 [3][4].
> 
> Hope this helps:
> 
> José Ferreiro
> 
> [1] - http://ws.apache.org/axis/
> [2] - http://ws.apache.org/wss4j/
> [3] - http://ws.apache.org/axis2/modules/rampart/1_0/security-module.html
> [4] - http://ws.apache.org/axis2/
> 
> 
> On Wed, Jun 18, 2008 at 11:12 AM, sh_santosh <[EMAIL PROTECTED]>
> wrote:
> 
>>
>> Hi Keith,
>>
>> I am using Axis1.3 version not Axis2.
>> So,is Rampart will work with Axis1.3 or it will work with only with Axis2
>> and higher versions.
>>
>> Thanks,
>> Ritesh.
>>
>> sh_santosh wrote:
>> >
>> > 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-not-present-in-the-incoming-message.-tp17960865p17976896.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]
>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Security-requirements-are-not-satisfied-because-the-security-header-is-not-present-in-the-incoming-message.-tp17960865p17980220.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]

Reply via email to