I am not exactly sure how to do it with the 1.0 release, but with the nightlies this is how I did it:

 

Authenticator authenticator = new Authenticator();

                                    List auth = new ArrayList();

                                    auth.add(Authenticator.BASIC);

                                    authenticator.setAuthSchemes(auth);

                                    authenticator.setUsername(username);

                                    authenticator.setPassword(password);

 

                                    Options options = new Options();

                                    options.setProperty(HTTPConstants.AUTHENTICATE, authenticator);

 

It seems to work J

 

Otherwise look at this article:

http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters#BASIC_AUTHENTICATION

 

Not sure if that is the 1.0 release or not

 

Roshan Punnoose

Phone: 301-497-6039


From: Charak, Vikas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:37 AM
To: [email protected]
Subject: RE: Basic Auth using the 1.0 release (not nightlies)

 

Mark,

I guess this class has undergone few changes in nightilies. I guess Axis2 designers can answer your question if they are reading this email.

 


From: Mark McCall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:28 AM
To: [email protected]
Subject: RE: Basic Auth using the 1.0 release (not nightlies)

 

I looked in org.apache.axis2.transport.http and I do not see HttpTransportProperties.BasicAuthentication.  I did find HttpTransportProperties.Authenticator, but I am not entirely sure how to use it.  Assuming I am to create an instance of HttpTransportProperties.Authenticator and set the username and password values, then what do I do with that instance?

 

As per my original question, is it possible to do this with the 1.0 release?  While I understand the 1.0 release is undergoing many bug fixes right now, the client libraries have been working quite well for us and we are a little apprehensive to switch to something that is undergoing change on a daily basis.

 

Thanks,

Mark

 


From: Charak, Vikas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 9:18 AM
To: [email protected]
Subject: RE: Basic Auth using the 1.0 release (not nightlies)

 

I guess look in to MessageContext and HttpTransportProperties.BasicAuthentication in nightly builds.

 

 

 


From: Mark McCall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 03, 2006 8:35 AM
To: [email protected]
Subject: RE: Basic Auth using the 1.0 release (not nightlies)

 

OK – I guess the resounding silence means “no”.  Is there a way to do this WITH the nightly builds?

 

Thanks,

Mark

 


From: Mark McCall
Sent: Monday, October 02, 2006 1:16 PM
To: '[email protected]'
Subject: Basic Auth using the 1.0 release (not nightlies)

 

I have not found any documentation or samples showing how to programmatically set Basic Auth information in an Axis2 generated client.  I am using the 1.0 release, not the nightly builds.  Can somebody point me in the right direction?

 

Thanks,

Mark




The information contained in this e-mail message is intended only
for the personal and confidential use of the recipient(s) named
above. This message may be an attorney-client communication and/or
work product and as such is privileged and confidential. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and
that any review, dissemination, distribution, or copying of this
message is strictly prohibited. If you have received this
communication in error, please notify us immediately by e-mail, and
delete the original message.

BEGIN:VCARD
VERSION:2.1
N:Punnoose;Roshan
FN:Punnoose, Roshan
ADR;WORK:;2115
LABEL;WORK:2115
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:20050413T183207Z
END:VCARD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to