I've asked variations of this question every now and then.  In one particular intstance, I didn't want a redirect to WindowsSignin.aspx.  In this particular instance, I'm interested if there's a way to force a redirect to WindowsSignin.aspx.  I.e. I might have a use case where I only want Windows Users to be able to login, and I don't want anyone to have an opportunity to see the Login.aspx page which usually appears if I visit the website the second time that I try.  Presumably upon first visiting /dotnetnuke, I get a cookie that gets set and I get redirected to WindowsSignin.aspx.  So if I cancel, and then visit /dotnetnuke again, I see the login dialog (which I don't want to see).  Let me know if it's possible to force a redirect to WindowsSignin.  Thanks.

Patrick

I believe I mean to force the IIS Sign-in.

I would have to say there is and isn't....

You "can" restrict the website to strictly AD users only, simply remove more the anonymous access from IIS and if they are not authenticated to the webserver they will not even be able to open website.  But, I'm not entirely sure it will authenticate properly to DNN unless the user hits the WindowsSignIn.aspx file one way or another.

You "cannot" redirect all users to the WindowsSignIn.aspx file directly through IIS.  You can push a URL out as a favorite or as a link and have people redirected to it that way, but you if you try to redirect ALL traffic to that file you will run into problems as you only need to redirect them there once to get authenticated and after that you don't want to redirect them there again until they need to be re-authenticated.  So, a mass redirect will cause major problems.  You will need to either redirect a specific URL that you post somewhere or you force them to use a favorite.

On a related note, has anyone tried using the DNN splash page to redirect users once per-session?  Maybe an iLink module on a splash page would suffice.