You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Manjula Peiris <ma...@wso2.com> on 2008/11/12 03:01:43 UTC
RE: Adding additional authentication mechanism to a axis c client
application
A module can be used if your authentication mechanism is at SOAP level.
If it is an http level authentication mechanism you have to change
http_sender.c .
On Tue, 2008-11-11 at 16:21 -0500, Kevin Heneghan wrote:
> Is there any mechanism for plugging in addition authentication logic?
>
>
> Can this be done using modules?
>
>
>
> Or is the only way to change the code in axis2_http_sender.c?
>
>
>
> Thanks
>
> Kevin
>
>
>
>
>
>
> ______________________________________________________________________
> From: Supun Kamburugamuva [mailto:supun06@gmail.com]
> Sent: Sunday, November 09, 2008 11:57 AM
> To: Apache AXIS C User List
> Subject: Re: Adding additional authentication mechanism to a axis c
> client application
>
>
>
>
> In that case you should implement this in to the axis2_http_sender.
>
> Supun.
>
> On Sat, Nov 8, 2008 at 6:04 PM, David Taylor (Lowell)
> <dk...@f5.com> wrote:
>
> 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:supun06@gmail.com]
> 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 <kh...@f5.com>
> 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
>
>
>
>
>
> --
> Software Engineer, WSO2 Inc
> http://wso2.org
> Web Services with Axis2/C http://wsaxc.blospot.com
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org