Mike, et al,

I need the ability to leverage the AD provider on child portals. In the previous version of the provider I simply included the WindowsSignin.aspx and WindowsSignin.aspx.vb files in the folder created when a child is created and removed anonymous permission. I then created a link on my page pointing to the WindowsSignin.aspx page like this:  http://ParentName/ChildName/WindowsSignIn.aspx. This worked very well for me since all my users log into our AD Domain with a Common Access Card, NOT a UserName and Password. In fact, SmartCard Login is mandated in my environment.

My reasons for using a parent/child configuration is because we are required to have an SSL certificate on all INTRANET web sites. Fine, but when you have 140 web sites and a finite number of IP Addresses you must consolidate to conserve (Shared SSL is not an option).

Now that the AD Provider has been seperated I need to devise a new solution. If anyone is operating similarly to this I would be greatful to hear your solution. Any and all suggestions are also welcome.

Finally, if AD Authentication is enabled I would like the login link automatically TRY to login first with the WindowsSignIn.aspx file before anything else.  If it fails then allow it to fall back to the standard login screen. Anyway, thanks for listening.

Jon