NT Authentication information

[somanivivek]

We have a intranet based web application for loading documents. The application is developed in ASP and allows only the users in the network domain to upload files. When user access the site,there is silent NT authentication.

Docs are loaded and associated information is filled in. Multiple documents can be loaded.
Sometimes the number of documents to be loaded is large and the session times out. After filling in lot of information, when the user press button to upload files, the user is confronted with a authentication pop-up asking for username / password / domain.

Even if the user gives correct values for the authenticatino pop-up, it does not authenticate. User need to close the browser and then visit the site again.

This is quite painful as the docs brwosed for loading and the information filled is lost.

What is happening here?

IS there a better way to do this ?

 

[CassidyHunt]

All you ever wanted to know about ADSI and more.

http://msdn.microsoft.com/library/d...s/adsi/adsi/iadsopendsobject_opendsobject.asp

If I were going to authenticate to the operating system I would use a COM+ component to handle the actual authentication and then cache the information in a static cookie on the client machine to be used in the future. There a lot of ways to handle this, but the one I am most successful at using is a COM object cookie combo.

Hope this helps.

Cassidy

 

[TheCandyman]

Kind of a non coding way to do it, if the ASP page is on an intranet, why don't you set the session timeout longer? It's an easy setting in IIS.

This way it won't time out and you don't have to worry about it.