Both (client & server) wont work when you use the websphere Application Server (=WAS) native web service stack and tools... When using the native WAS (6.1) WS stack you can secure web service using specific descriptors. AST help you to do that.
If you want to propagate identity, IBM call that "Identity Assertion". You have several possible way to do "identity assertion", one of them is using a username token to propagate the user identity. The jaas subject is automatically generated by WAS Note that a second token and a signature may be added to secure the message. The generated username token won't in this case have a PASSWORD tag, and the server wont accept one. In short: It will work if you do not have a password tag. It will not work correctly if you have a password tag with a null password: websphere will not consider that as a identity assertion. I am not sure my explanation is clear ... :-/ Marc On Fri, 2008-01-04 at 16:39 +0100, Marcel Ammerlaan wrote: > Hi, > > On Jan 4, 2008 12:33 PM, Marc Jadoul <[EMAIL PROTECTED]> > wrote: > I do not completely understand who develop wss4j... last times > I checked it seemed nothing really replaced it... but several > times people proposed to help and nothing changed... > strange... > > Note that adding a null password won't work with some > infrastructure (Websphere). > > Do you mean as a server or as a client? I've got it working with .Net > using both server and client mode and am currently looking at using > WebSphere. In my case the solution should be usable both as a client > and a server, so do you mean that WebSphere will not accept such a > message or will it not generate it (in the second case, this is not > really a problem, the service producer should just ignore it). > > Regards, > > Marcel Ammerlaan. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
