Authentication againts ADS

2 Oct 2008 9:20 AM

Michel777

Dear members,

I need some inputs for the following scenario:

(1) the java application (JAPP) running on Windows XP, which is part of an
NT-Domain
(2) the user (USER) on this box is logged in the NT-Domain
(3) the JAPP access a server (SERVER) via HTTP / HTTPS
(4) the SERVER should be authenticate the USER againts ADS without requiring
password from USER ans without using Kerberos.

Is there any way ? Perhaps using NTLM ?

Thanks in advance,

Michel

4 Oct 2008 8:11 AM

David Wang

On Oct 2, 2:20 am, Michel777 <Michel***@discussions.microsoft.com>
wrote:
Show quoteHide quote

> Dear members,
>
> I need some inputs for the following scenario:
>
> (1) the java application (JAPP) running on Windows XP, which is part of an
> NT-Domain
> (2) the user (USER) on this box is logged in the NT-Domain
> (3) the JAPP access a server (SERVER) via HTTP / HTTPS
> (4) the SERVER should be authenticate the USER againts ADS without requiring
> password from USER ans without using Kerberos.
>
> Is there any way ? Perhaps using NTLM ?
>
> Thanks in advance,
>
> Michel

The Java Application is no different than a BROWSER in this case and
is able to authenticate the user to the server automatically using any
authentication protocol that you see working with normal browsers.

However, it is the user application's responsibility to do the auto-
logon to the server. There is no such thing as "the server should be
authenticate the user against ADS without requiring password". Servers
have no magic. The client is always responsible for
[pre]authenticating to the server.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

5 Oct 2008 9:57 AM

David Wang

On Oct 2, 2:20 am, Michel777 <Michel***@discussions.microsoft.com>
wrote:
Show quoteHide quote

> Dear members,
>
> I need some inputs for the following scenario:
>
> (1) the java application (JAPP) running on Windows XP, which is part of an
> NT-Domain
> (2) the user (USER) on this box is logged in the NT-Domain
> (3) the JAPP access a server (SERVER) via HTTP / HTTPS
> (4) the SERVER should be authenticate the USER againts ADS without requiring
> password from USER ans without using Kerberos.
>
> Is there any way ? Perhaps using NTLM ?
>
> Thanks in advance,
>
> Michel

The Java application is no different than a Web Browser in your
scenario. Anything you observe the web browser can do, you can re-
implement in your Java application using standard, open protocols and
APIs.

FYI: There is no such thing as what you want in #4. The server always
requires authentication. The issue is whether the web client is able
to automatically provide it. If the web client (i.e. Java application)
fails to do so, then some form of authentication prompt has to be
raised to the user.

//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

7 Oct 2008 3:53 PM

Michel777

Hi David,

thanks a lot. In our case ois teh server also our product. The main question
is, how to send the the three parameters to the domain controller for the
authentication. See step 5 in document:

http://msdn.microsoft.com/en-us/library/aa378749.aspx#

Thnak s alot in advance,

laszlo

Show quoteHide quote

"David Wang" wrote:

> On Oct 2, 2:20 am, Michel777 <Michel***@discussions.microsoft.com>
> wrote:
> > Dear members,
> >
> > I need some inputs for the following scenario:
> >
> > (1) the java application (JAPP) running on Windows XP, which is part of an
> > NT-Domain
> > (2) the user (USER) on this box is logged in the NT-Domain
> > (3) the JAPP access a server (SERVER) via HTTP / HTTPS
> > (4) the SERVER should be authenticate the USER againts ADS without requiring
> > password from USER ans without using Kerberos.
> >
> > Is there any way ? Perhaps using NTLM ?
> >
> > Thanks in advance,
> >
> > Michel
>
>
> The Java application is no different than a Web Browser in your
> scenario. Anything you observe the web browser can do, you can re-
> implement in your Java application using standard, open protocols and
> APIs.
>
> FYI: There is no such thing as what you want in #4. The server always
> requires authentication. The issue is whether the web client is able
> to automatically provide it. If the web client (i.e. Java application)
> fails to do so, then some form of authentication prompt has to be
> raised to the user.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>