aassif wrote:
Now moving to the Server side implementation, I was expecting retrieving
the result will be simple so I tried on the lines similar to Axis 1.X,
below is the code listing:
[znip code]
I don't know which is the preferred procedure for extracting authentication
data from
Dear Geir,
Thank you for your reply. Your solution for OC4J was not working with
Tomcat. I managed to make it work after getting ideas from your last reply
which was using HttpServletRequest. Below is the working solution, which may
help other readers.
// acquire the active HTTP
Dear Geir Amdal,
Thank you for reply. I have one query regarding Basic Authentication. I
Axis 1.X, when we use Call.setUserName() or call.setPassword(), the details
are encoded and sent to the server as HTTP Headers and which can be seen
through TCP monitor. The username and password can be
aassif wrote:
I have one query regarding Basic Authentication. I Axis 1.X, when we use
Call.setUserName() or call.setPassword(), the details are encoded and sent
to the server as HTTP Headers and which can be seen through TCP monitor.
The username and password can be retrieved in the Web
Hi,
Thank you for your reply. I will try again today, but yesterday when I
tried with different set of options the HTTP Header remained the same for
each Web Service call. I assume that I must be missing something.
Thank you for the help.
Cheers
Asif
--
View this message in context:
Dear Geir,
If no Authorization header is present among the HTTP headers, I'd
suspect the ServiceClient used by the stub was not configured correctly...
One stupid question, do I need to manually configure ServiceClient to
use Basic Authorization.
Cheers
Asif
--
View this
aassif wrote:
[...] do I need to manually configure ServiceClient to use Basic
Authorization.
I might be missing the mark here, but are you asking whether you have to
instanciate a new ServiceClient or whether you can configure one retrieved
from the stub? If so, take a look at Belunek
Dear Geir,
Thank you for your help. I was doing exactly the same what was mentioned
in the Thread and what you suggested today but yesterday I failed to notice
the HTTP headers regarding Authorization: Basic. But today when I executed
the client without any change it was working as required.
Dear Geir,
Thank you for your help. I was doing exactly the same what was mentioned
in the Thread and what you suggested today but yesterday I failed to notice
the HTTP headers regarding Authorization: Basic. But today when I executed
the client without any change it was working as required.
Hi,
I went through the whole discussion and when tried to implement BASIC
Authentication I can't find the Authenticator class, the one which I can
locate is only HttpTransportProperties.Authenticator. But
HttpTransportProperties.Authenticator doesn't have any property BASIC and
seems to be
aassif wrote:
I went through the whole discussion and when tried to implement BASIC
Authentication I can't find the Authenticator class, the one which I can
locate is only HttpTransportProperties.Authenticator.
It was HttpTransportProperties.Authenticator that was used. My apologies for
On 11. apr. 2007, at 14:52, Belunek Karel wrote:
I have Axis2 1.1.1 under Tomcat 5.5.9 and I have correctly working
Axis service generated from WSDL file.
Now I'm trying to implement BASIC authenticacion.
On server side I'have se security constraint on the Tomcat level,
it works fine. I
On 12. apr. 2007, at 13:25, Jarek Kucypera wrote:
Don't you also need to set the 'preemtive' flag, like this:
authenticator.setPreemptiveAuthentication(true);
?
Ahh. Valid point. Though I am not sure a 'need' can be generalized
for this setting.
From what I can tell, setting this flag
Geir Amdal napsal(a):
On 11. apr. 2007, at 14:52, Belunek Karel wrote:
I have Axis2 1.1.1 under Tomcat 5.5.9 and I have correctly working
Axis service generated from WSDL file.
Now I'm trying to implement BASIC authenticacion.
On server side I'have se security constraint on the Tomcat level,
14 matches
Mail list logo
