H Paul wrote:For your original post:
Ivan Krizsan wrote:Hi!
I don't know the cause for your problems, but I would proceed as follows:
1. Using soapUI, I would issue a request from the client computer.
This is to learn what a working request looks like.
2. Using TCPmon, WireShark, Membrane or some other tool, examine the requests from the client.
3. Manipulate the client code until the requests look like the requests from soapUI.
H Paul wrote:1. IF the server side is "configured correctly" for basic auth,
then if the client does not send the user/password
OR if the client does send the incorrect user/password
then the server will return to client send back 401 Error: Unauthorized.
Even if the server did not the return the AxisFault to the client,
the server must have logged the error some where in the server side log.
2. Have you looked into the server's log? to see what type of error/exception.
ffdc log folder
Jimmy Clark wrote:Is the problem with the authentication or is the problem with the web service or is the problem with the network communication?
I would make sure that the web service is working without the authentication part or the network part. Run a local client on the same node as the service. If this work, then try to call the web service from the remote node without authentication. If this works, then your problem is located in the authentication. If it doesn't work, then you have a problem with the web service.
Since my application is external to this application (though within the same intranet), I have to go through TAM authentication layer.
Net communication is also ruled out.
Now with respect to your first question "Is the problem with the authentication", I am confused how to respond. I am sure the credentials, I am supplying is clean and it is being passed in request header. Now the question is whether TAM is reading the request header and authenticating my request? If not, then obviously TAM would reject all my requests.
I am going to verify with the team who is handling TAM authentication layer. But in between do you know of any better approach of getting authenticated with TAM?
Nischit Shetty wrote:Hi All - We were able to fix the issue. The issue turned out be a problem with TAM layer itself. It was configured incorrectly because of which it was only allowing browser based requests to pass through. We then switched to a different environment where TAM was better configured and it worked.
Just FYI, the following piece of AXIS code satisfies BASIC authentication for TAM -
Humans and their filthy friendship brings nothing but trouble. My only solace is this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!https://www.kickstarter.com/projects/paulwheaton/greenhouse-1