No, you don't need WSSecurity to do HTTP DIGEST auth.

The original code you posted will work with Digest as well. Basically
the code will try basic first then digest. If it does not work with
latest nightly build. Please log a JIRA bug and we will fix it.

thanks,
dims

On 8/9/06, Vinh Tran <[EMAIL PROTECTED]> wrote:




Quick question Martin…



Does this mean I will no longer be using HTTP/DIGEST and instead be using
WS-Security? If so, is there a way to do HTTP DIGEST in Axis2?



Thanks



 ________________________________


From: Vinh Tran [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, August 09, 2006 9:34 AM
 To: [email protected]; Martin Gainty
 Subject: RE: [Axis2] Client Digest Authentication



So I will need to use Rampart for DIGEST authentication. Got it.



Thanks Martin.



 ________________________________


From: Martin Gainty [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, August 09, 2006 9:29 AM
 To: [email protected]
 Subject: Re: [Axis2] Client Digest Authentication




Good Morning Tran-





that example was dated


The security functionality has been split to project WSS4J


http://ws.apache.org/wss4j/





Once you download and onstall you will see a TestHarness that tests Digest
Functionality located at


/test/wssec/TestWSSecurityNew5.java



 The test Function to test Digest tokens is called testUsernameTokenDigest


HTH,
 Martin--


*********************************************************************
 This email message and any files transmitted with it contain confidential
 information intended only for the person(s) to whom this email message is
 addressed.  If you have received this email message in error, please notify
 the sender immediately by telephone or email and destroy the original
 message without making a copy.  Thank you.










----- Original Message -----


From: Vinh Tran


To: [email protected]


Sent: Wednesday, August 09, 2006 9:07 AM


Subject: RE: [Axis2] Client Digest Authentication




Martin,



I do not see the org.apache.axis.security.servlet package
nor do I see MessageContext.SECURITY_PROVIDER. Is this
something that was added recently? I am currently using a snapshot from
July.



Also, by merely using SECURITY_PROVIDER does this get me DIGEST
authentication?



Thanks.



 ________________________________


From: Martin Gainty [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, August 08, 2006 9:10 PM
 To: [email protected]
 Subject: Re: [Axis2] Client Digest Authentication




Tran-





SECURITY_PROVIDER is an attribute of MessageContext


Here is an example for you


http://rifers.org:8088/viewrep/~raw,r=1175/rifers/rife/trunk/src/framework/com/uwyn/rife/engine/elements/SoapAxis.java


Best Regards



 Martin --


*********************************************************************
 This email message and any files transmitted with it contain confidential
 information intended only for the person(s) to whom this email message is
 addressed.  If you have received this email message in error, please notify
 the sender immediately by telephone or email and destroy the original
 message without making a copy.  Thank you.










----- Original Message -----


From: Vinh Tran


To: [email protected]


Sent: Tuesday, August 08, 2006 8:12 PM


Subject: [Axis2] Client Digest Authentication




I am able to get basic authentication working with Axis2 but would now like
to switch to digest.



With BASIC I do the following:



HttpTransportPorperties.BasicAuthentication basicAuth = new
HttpBasicTransportProperties().new BasicAuthentication();

basicAuth.setUsername(_username);

basicAuth.setPassword(_password);

options.setproperty(org.apache.axis2.transport.http.HTTPConstants.BASIC_AUTHENTICATION,
basicAuth);



How is this accomplished with DIGEST authentication? There doesn't appear to
be a DigestAuthentication class or an http constant
HTTPConstants.DIGEST_AUTHENTICATION.



Thanks.






--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to