| Author: Ritesh N. Jain 02 Sep 2008 | Member Level: Gold | Rating:  Points: 1 |
replace <allow users ="?"/> with <deny users ="?"/> and check if its work or not.
|
| Author: Krishnamoorthy 03 Sep 2008 | Member Level: Bronze | Rating: Points: 6 |
Before posting into a forum anybody will make all possibilties,
to find a better solution.
You are telling me to change it with "deny".
Believe me, before posting here, I have tried all the combinations of "allow" and "deny" even with IIS settings also.
I THINK "Integrate Window Authentication" WILL NOT SHOW ANY DIALOG AND IT WILL ONLY TAKE THE LOGGED IN CREDENTIALS (OR BASED ON IIS SETTING CRENTIALS) ONLY. "?" MEANS "ANONYMUS" THATS IT!!!. ONLY BASIC OR DIGEST WILL POPUP A DIALOG.
If I'm wrong, I bet you, can you take it as challenge and get solution for the above stated problem?
|
| Author: Ritesh N. Jain 03 Sep 2008 | Member Level: Gold | Rating: Points: 6 |
it's good to know you did your r&d before posting here unlike other memeber do.
well as far your query is concern,the main idea behind windows authentication is to make sure all the user accessing webapplication (that implements Windows Authentication )in intranet environment must be a valid memeber of Domain user.Hence if any user is already loged-In into the Domain/Intranet using his domain account and trying to access your application than IIS itself will verify the user's credential and if he belong to domain user group he will not get "Authentication Dialog" box.
As oppose consider the case where someone came to your office and just plug in his laptop into your network and login into his local machine account and try to access your application ofcourse he will prompt for "Authentication Dialog".
I am sure you must be aware of this but in case not just check it out value of User.Identity.Name whenever you get request from any user who is logged in using domain account,i am sure you will get proper valid user name for this.
|