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:[EMAIL PROTECTED] > 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) > <[EMAIL PROTECTED]> 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:[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 > > > > > > -- > Software Engineer, WSO2 Inc > http://wso2.org > Web Services with Axis2/C http://wsaxc.blospot.com > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xs:any minOccurs Check is Wrong
I have a WSDL that I am using to generate ADB stubs. This WSDL includes
a type with xs:any that is causing the stub to have code generated to
check for at least 1 element in the list, even though the element lists
minOccurs="0". Here's the fragment of the WSDL:
Here is the erroneous check in the generated stub deserialize function:
if (i < 1)
{
/* found element out of order */
AXIS2_LOG_ERROR(env->log,
AXIS2_LOG_SI, "ItemListTypeSequence (@minOccurs = '1') only have %d
elements", i);
if(element_qname)
{
axutil_qname_free(element_qname,
env);
}
if(arr_list)
{
axutil_array_list_free(arr_list,
env);
}
return AXIS2_FAILURE;
}
The problem appears to be that the XSLT stylesheet is looking for an
@any attribute to be set, to avoid generating this section of code. It
seems that the xs:any element should set this attribute. However, I
can't figure out where that attribute should be set. Any help would be
greatly appreciated.
Thanks,
-David
RE: Adding additional authentication mechanism to a axis c client application
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:[EMAIL PROTECTED] 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) <[EMAIL PROTECTED]> 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:[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 -- Software Engineer, WSO2 Inc http://wso2.org Web Services with Axis2/C http://wsaxc.blospot.com
