unfort ... still no luck ...: here goes : request : ========= <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"; 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";> <soap:Header> <wsa:Action> </wsa:Action> <wsa:MessageID>uuid:15a2ef5c-408f-411e-9e82-b66ba0216076</wsa:MessageID> <wsa:ReplyTo> <wsa:Address>http://schemas.xmlsoap.org/ws/2004/03/addressing/role/anonymous</wsa:Address> </wsa:ReplyTo> <wsa:To>http://localhost:8080/axis/services/stock-wss-01</wsa:To> <wsse:Security soap:mustUnderstand="1"> <wsu:Timestamp wsu:Id="Timestamp-89ae3aaa-f8bc-4b2f-a866-fd22a252f8fd"> <wsu:Created>2006-11-11T14:34:02Z</wsu:Created> <wsu:Expires>2006-11-11T14:39:02Z</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-5f1c6b24-b5cd-48a6-8224-7ab128e348d7"> <wsse:Username>wss4j</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>security</wsse:Password> <wsse:Nonce>7lQDoG6gSUUf/md/2M1LLg==</wsse:Nonce> <wsu:Created>2006-11-11T14:34:02Z</wsu:Created> </wsse:UsernameToken> </wsse:Security> </soap:Header> <soap:Body /> </soap:Envelope>
response: ========= <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <soapenv:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="Timestamp-20859482"><wsu:Created>2006-11-11T14:34:13.656Z</wsu:Created><wsu:Expires>2006-11-11T14:39:13.656Z</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="UsernameToken-23903639"><wsse:Username>wss4j</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText";>security</wsse:Password><wsse:Nonce>gPFA1VC7EAPxq0ZJLJZ1dA==</wsse:Nonce><wsu:Created>2006-11-11T14:34:13.636Z</wsu:Created></wsse:UsernameToken></wsse:Security></soapenv:Header><soapenv:Body><testReturn>Just a test</testReturn></soapenv:Body></soapenv:Envelope> trust me ... i have tried almost all combinations and sequences ... maybe i shd try wse3.0 (eek !) ? :) --- Ruchith Fernando <[EMAIL PROTECTED]> wrote: > Hi, > > On 11/11/06, ws_dev2001 <[EMAIL PROTECTED]> > wrote: > > Hey Ruchith, > > Are you saying Rampart+Axis2 is what I must look > at ? > > We have WS-Security support for both Axis1.x and > Axis2. > I'm not sure about any other documentation on Axis > 1.x other than what > is available with wss4j and in the wiki [1],[2],[3]. > > However we do have some articles/tutorials on Axis2 > + rampart stuff :-) > > Thanks, > Ruchith > > [1] http://wiki.apache.org/ws/FrontPage/WsFx/wssec > [2] > http://wiki.apache.org/ws/FrontPage/WsFx/wss4jFAQ > [3] > http://wiki.apache.org/ws/FrontPage/WsFx/wss4jParameters > > I think the problem is with the qname in wse2.0 > sp3... > > unfortunately i am not brave enough to upgrade to > > wse3.0 right now ... > > :) > > --- Ruchith Fernando <[EMAIL PROTECTED]> > > wrote: > > > > > Hi Dev, > > > > > > > > > > > > On 11/11/06, ws_dev2001 <[EMAIL PROTECTED]> > > > wrote: > > > > Hi Ruchith, > > > > Axis engine with wss4j plugged in is happy > with > > > the > > > > relevant code commented out for the call in > > > > WSDaAllReceiver : > > > > ... > > > > if (!checkReceiverResults(wsResult, actions)) > { > > > > ... > > > > > > > > > > If this is the point where WSS4J complains .. > seems > > > like you have to > > > configured your "action" parameter properly. > > > > > > Please send a message generated by the .NET > client, > > > we should be able > > > to figure out the security actions performed on > the > > > message. > > > > > > > Maybe you can guide me to some resourceful > > > > documentation on this ..etc. ? > > > > > > If you are planning to switch to Axis2 from Axis > > > 1.x, you can find > > > documentation related to Axis2 security stuff in > > > www.wso2.net > > > > > > Thanks, > > > Ruchith > > > > > > -- > > > www.ruchith.org > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > > > Send instant messages to your online friends > http://uk.messenger.yahoo.com > > > > > -- > www.ruchith.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
