Precisely I'm trying this at this time, but most links you can get about interoperability-work between platforms (.net - java ) is shown using windows communication foundation + .net 3.0/3.5 in the .net side. If you need a choice in the client side, I think WCF is a better choice. In the case of server side, an api that can expose your policies as a mex (like https://wsit.dev.java.net/ metro , or axis-2 + some other configuration does), is a good candidate.
About interoperability with wse-3.0 in the .net (client side), here is a link that can help you (take in mind that this service example does not show the secure conversation that you can enable with the wse-3.0 wizard: http://www.shellysaunders.co.uk/Blog/tabid/65/EntryID/2/Default.aspx http://www.shellysaunders.co.uk/Blog/tabid/65/EntryID/2/Default.aspx (this does not shown the flag establishSecurityContext enabled as you can, as described in the Hands On Labs of wse-3 about security: http://www.microsoft.com/Downloads/details.aspx?familyid=018A09FD-3A74-43C5-8EC1-8D789091255D&displaylang=en ) José Ferreiro wrote: > > Hello, > > Do you think this configuration could work? > > Client side : .net 2.0 wse 3.0, authentication using: x.509 > server side : axis2, rampart + rahas, authentication using: x.509, > > Is there any example or article? > > Thank you in advance for your answers > > > On Jan 18, 2008 2:08 AM, ahurtado <[EMAIL PROTECTED]> wrote: > >> >> I have seen that for web service secure conversation: >> + for axis1 there are some classes in wss4j and in wss4j-sandbox that >> indicates that "once upon a time" was some interest for do that (this is, >> enable axis 1 for secure conversation), but i have not found a concrete >> sample working doing this, specially if you want to integrate the web >> service with .net 2.0 + web service enhancements (wse-3.0), mantaining >> x.509 >> security certificates enabled at the same time. >> + for axis2, you can use rampart + rahas for this support, but the >> sample >> uses x.509, I think that you need to configure the services.xml of the >> sample to make it work with usernametoken ( <wsp:Policy> section ). you >> can >> explore http://www.mssoapinterop.org/ilab/ to find some samples for write >> this section. >> >> >> Anil Misra wrote: >> > >> > Hi, >> > >> > I have the same requirement and I see no reply to the question below, >> > if some has a sample please let me know. >> > >> > Thanks, >> > -Anil Misra >> > >> > >> > ------------ >> > Hi Ruchith, >> > >> > Do you have please sample configuration where the base token in RST is >> > usernametoken instead of x509? >> > >> > Thank you, >> > Elena >> > >> > ----- Original Message ---- >> > From: Ruchith Fernando <[EMAIL PROTECTED]> >> > To: axis-user@ws.apache.org >> > Sent: Tuesday, February 13, 2007 9:25:28 AM >> > Subject: Re: Ws-secureconversation rampart samples >> > >> > >> > Hi Elena, >> > >> > Please have a look at "policy/sample04" in the samples directory of >> > the rampart-1.1 release. >> > >> > Thanks, >> > Ruchith >> > >> > On 2/11/07, Elena Neroslavskaya <[EMAIL PROTECTED]> wrote: >> >> >> >> Hello, >> >> >> >> I'm looking to implement an axis client establishing and canceling >> > security >> >> context >> >> with ws-secureconversation protocol. Do you have a code sample sending >> > RST, >> >> using context and cancelling it in Rampart? >> >> >> >> >> >> Any tutorial or sample will be very helpful, >> >> >> >> thank you in advance, >> >> Elena >> >> >> > >> > >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Ws-secureconversation-rampart-samples-tp14807694p14942019.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/Ws-secureconversation-rampart-samples-tp14807694p14949166.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]
