W
Will
We have a java web application that calls web services on other
machines (SOA). The browser authenticates to IIS using Integrated
Windows Authentication (IWA) using the NTLM protocol to the web
application. The web services require the same type of authentication,
but we are unable to forward the credetials from the web application
(received from the browser) to the web service calls. The calls fail
with a HTTP 401 error.
We are using Apache Jakarta Commons HttpClient. It has parameters to
forward the NTLM info, however the password is required... and that is
unattainable, without prompting the user... which we do not wish to do.
..NET has the ability to forward the credentials via the
System.Net.CredentialCache.DefaultCredentials object, without actually
needing access to the password.
The customer will not change the authentication architecture. Can this
nut be cracked with Java. They do not wish to run IIS or the Java
Application Server as a valid domain user either.
machines (SOA). The browser authenticates to IIS using Integrated
Windows Authentication (IWA) using the NTLM protocol to the web
application. The web services require the same type of authentication,
but we are unable to forward the credetials from the web application
(received from the browser) to the web service calls. The calls fail
with a HTTP 401 error.
We are using Apache Jakarta Commons HttpClient. It has parameters to
forward the NTLM info, however the password is required... and that is
unattainable, without prompting the user... which we do not wish to do.
..NET has the ability to forward the credentials via the
System.Net.CredentialCache.DefaultCredentials object, without actually
needing access to the password.
The customer will not change the authentication architecture. Can this
nut be cracked with Java. They do not wish to run IIS or the Java
Application Server as a valid domain user either.