If you have the option of switching please do so. Cause Axis2 should have much better support for this than Axis. I'll let a rampart expert answer your question on whether this is a common security theme. Does the WSDL advertise these security requirements using policy? If so it should be easier.
Thanks, Keith. On Tue, Sep 30, 2008 at 2:46 AM, Steve Cohen <[EMAIL PROTECTED]> wrote: > Actually, I meant original axis 1.4. > > However, if you tell me that support for this functionality is much > stronger in axis 2, or non-existent in original axis, I might consider > switching. > > > > Mary Thompson wrote: > >> If you mean axis2 1.4, the Rampart module will do that for you. The Axis >> pages link to some documentation and to the rampart 1.3 module. Go to >> http://ws.apache.org/rampart/download/1.4/download.cgi for rampart 1.4 >> and more documentation. >> >> After you have read the overviews, look at the rampart/samples code. I >> think samples/basic/sample03 may do what you want. >> >> Mary >> >> Steve Cohen wrote: >> >>> I am trying to generate java Client code to access a web service from a >>> WSDL using axis 1.4. Documentation that comes with the WSDL expects me to >>> generate packets with SOAP headers that look something like this. >>> >>> Is this a well-known security scheme that Axis can be easily configured >>> to generate or must it be coded by hand? >>> >>> <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/08/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>urn:uuid:xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</wsa:MessageID> >>> >>> <wsa:ReplyTo> >>> <wsa:Address> >>> >>> http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous >>> </wsa:Address> >>> </wsa:ReplyTo> >>> <wsa:To>https://{url:443}</wsa:To> >>> <wsse:Security soap:mustUnderstand="1"> >>> <wsse:UsernameToken xmlns:wsu=" >>> http://docs.oasis-open.org/wss/2004/01/oasis- >>> 200401-wss-wssecurity-utility-1.0.xsd" >>> wsu:Id="SecurityToken-xxxxxxx-xxxx-xxxx- >>> xxxx-xxxxxxxxxxxx"> >>> <wsse:Username>[username]</wsse:Username> >>> <wsse:Password >>> Type=" >>> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username- >>> token-profile-1.0#PasswordText"> >>> [password] >>> </wsse:Password> >>> </wsse:UsernameToken> >>> </wsse:Security> >>> </soap:Header> >>> <soap:Body> >>> ... </soap:Body> >>> </soap:Envelope> >>> >>> >>> >>> --------------------------------------------------------------------- >>> 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] >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
