windows authentication

[logi2000]

i have an intranet application. the first time i acces the application from the web server, a pop up windows shows up, asking for the userid, password and domain, i fill the information, and the requested page shows up, this same thing happens when i access the application from a client PC, but if the user puts his windows id and password the requested page of the application does not show.

how can i configure my application, in order to avoid this security window to keep showing up ?

the iis is configured to use windows integrated security, and is not using anonymous access.

 

[Custom24]

Hi
I get such a dialog box with my Intranet windows auth app because the web server is on a different (and non-trusted) domain than my development box. So every time from my dev box I want to see the live app, I have to supply my credentials for the other domain. If this turns out to be your problem, then you will have to get your network guys to establish trust between the web server's domain and the client's domain.

I have never seen such a box pop up just when accessing the app locally. This makes me suspect that your web.config file is not set up correctly - in addition to IIS, you have to put this setting in the config file

<authentication mode="Windows" />

Hope this helps you.

Mark

 

[logi2000]

i am working in the same domain, and my web config has <authentication mode="Windows" />

 

[Custom24]

What about the authorization section of the web.config? If it is not already, try setting it to

<authorization>
<allow users="*" /> <!-- Allow all users -->
</authorization>

Are you using impersonation? (in the web.config file, it is set to <identity impersonate="true"/>) If so, could it be that your account has privileges to do something the app needs which the user account does not. It is a long shot - I would just expect the app to error when trying to use the user credentials.

Finally, another long shot. It is supposed to work that lower level config files take precedence over higher level ones. So for example, if your app was a sub directory of a web directory, and both had a web.config. The settings would pass down first from machine.config, then overridden by the outer directory web.config and then the inner web.config.

Failing that, you might want to just set up another asp.net app without windows auth and make sure the user can access that. It might be some systems or Active Directory problem. You could try rebooting the server. They are always changing little settings at our place without telling us which break stuff.

Hope you figure it out

Mark