Just an idea here: sometime .NET WSE configuration requires to include WS-Addressing (the wsa: tags) to work correctly, at least I saw some discussions about this requirement.
Regards, Werner > -----Ursprüngliche Nachricht----- > Von: ext sh_santosh [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 23. Juli 2008 07:53 > An: [email protected] > Betreff: Re: need help with axis/wss4j client with .net service > > > Hi Sean, > > Have you solved this problem ,as I am also facing the same > problem ,if you > have solved the problem ,please guide me also on this.My > client-deploy.wsdd > is same what you are using.Please reply as its very urgent > for me to get > through with this. > you can mail me on [EMAIL PROTECTED] > > Thanks and Regards, > Ritesh. > > Sean Kavanagh wrote: > > > > i'm having trouble migrating our axis/wss4j client to work with a > > new .NET service. > > > > i'm getting > > > > faultCode: > > > {http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec > urity-secext-1.0.xsd > > }InvalidSecurityToken > > faultSubcode: > > faultString: An invalid security token was provided > > faultActor: > > > https://applications.transcontinentaldirect.com/test/armyrotcl > eads/ws18/LeadsTransaction.asmx > > > > i'm using Axis 1.4 and WSS4j 1.5.3 > > > > here is my wsdd > > > > <deployment xmlns="http://xml.apache.org/axis/wsdd/"; > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java > > "> > > <transport name="http" > > pivot="java:org.apache.axis.transport.http.HTTPSender"/> > > <globalConfiguration> > > <requestFlow > > > <handler > > type="java:org.apache.ws.axis.security.WSDoAllSender" > > > <parameter name="action" value="UsernameToken"/> > > <parameter name="user" value="ws_test"/> > > <parameter name="passwordCallbackClass" > > value="com.goarmy.brc.transaction.web.PWCallback"/> > > <parameter name="passwordType" > value="PasswordText"/> > > <parameter name="mustUnderstand" value="1"/> > > <parameter name="addUTElements" value="Nonce > > Created" /> > > </handler> > > </requestFlow> > > </globalConfiguration> > > </deployment> > > > > i don't really have any visibility on whats going on the > server side > > of things or how its been configured.. I imagine that they are > > probably using WSE 3.0 with this new service. > > > > i was able to get the service provider to send me the soap > header for > > a working .NET client > > > > <soap:Header> > > > > > <wsa:Action>http://TranscontinentalDirect.com/WebServices/Army > /ARMSTransaction_Army/InsertTransaction > > </wsa:Action> > > > <wsa:MessageID>uuid:aa60429b-a0ac-4fb4-807c-4725b670b650</ > > wsa:MessageID> > > <wsa:ReplyTo> > > > > > <wsa:Address>http://schemas.xmlsoap.org/ws/2004/03/addressing/ > role/anonymous > > </wsa:Address> > > </wsa:ReplyTo> > > > > > <wsa:To>http://applications.transcontinentaldirect.com/test/ar > myrotcleads/ws18/LeadsTransaction.asmx > > </wsa:To> > > <wsse:Security soap:mustUnderstand="1"> > > <wsu:Timestamp > wsu:Id="Timestamp-5ced9be7-5cc1-456c- > > b00e-35b6a8a1986d"> > > > <wsu:Created>2008-01-29T19:51:45Z</wsu:Created> > > > <wsu:Expires>2008-01-29T19:56:45Z</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-17f69631-0c49-4759-ba57-aa8528b74c00"> > > <wsse:Username>ws_test</wsse:Username> > > <wsse:Password > > > Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss- > username-token-profile-1.0#PasswordText > > ">xxxxxx</wsse:Password> > > > <wsse:Nonce>UTeT6XeW+3TfMHc6ihJe9g==</wsse:Nonce> > > > <wsu:Created>2008-01-29T19:51:45Z</wsu:Created> > > </wsse:UsernameToken> > > </wsse:Security> > > </soap:Header> > > > > and here is the one that i'm sending through axis and wss4j... > > > > <soapenv:Header> > > <wsse:Security > > > xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-20040 > 1-wss-wssecurity-secext-1.0.xsd > > " soapenv:mustUnderstand="1"> > > <wsse:UsernameToken > > > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401 > -wss-wssecurity-utility-1.0.xsd > > " wsu:Id="UsernameToken-28591825"> > > <wsse:Username>ws_test</wsse:Username> > > <wsse:Password > > > Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss- > username-token-profile-1.0#PasswordText > > ">xxxxxx</wsse:Password> > > <wsse:Nonce>zR7G1oEFnnIIaQ0Din9jmA==</wsse:Nonce> > > <wsu:Created>2008-01-25T20:30:07.223Z</wsu:Created> > > </wsse:UsernameToken> > > </wsse:Security> > > </soapenv:Header> > > > > i was able to get axis/wss4j to work with their previous > service very > > easily.. but this ones got me stumped, any help you guys can give > > would be greatly appreciated... > > > > thank you!!! > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/need-help-with-axis-wss4j-client-with-.n > et-service-tp15189102p18604323.html > Sent from the WSS4J mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
