I think Kevin is asking about Negotiate authentication defined in RFC 4559. This is an HTTP transport level authentication scheme.
Thanks, -David -----Original Message----- From: Supun Kamburugamuva [mailto:[EMAIL PROTECTED] Sent: Fri 11/7/2008 9:40 PM To: Apache AXIS C User List Subject: Re: Adding additional authentication mechanism to a axis c client application Not familiar with NTLM. Is that a transport level auth mechanism or soap level auth mechanism? AFAIK kerboros is a SOAP level auth mechanism. To support kerboros authentication [1] needs to be implemented at the Rampart/C level. [1] http://www.oasis-open.org/committees/download.php/16788/wss-v1.1-spec-os-KerberosTokenProfile.pdf On Sat, Nov 8, 2008 at 12:32 AM, Kevin Heneghan <[EMAIL PROTECTED]> wrote: > Hi, > > > > I am creating a SOAP/WS-management client to talk to an existing web > service. The existing web service requires NTLM or Kerberos > authentication. How do I plugin my authentication code to the axis client > to negotiate authentication at the HTTP level? > > > > In detail. > > > > I have existing code that can do NTLM authentication in a share library on > linux. > > I have a SOAP/WS-management client that needs to utilize this library to > do NTLM authentication at the HTTP level. > > How do I put my code into the axis client to do the authentication? > > > > Thanks > > Kevin > -- Software Engineer, WSO2 Inc http://wso2.org Web Services with Axis2/C http://wsaxc.blospot.com
