Hoping someone can shed some light on this.  After I upgraded my site from 4.4.1 to 4.5.3 to 4.6.2, it would no longer build (compile) without errors in Visual Web Developer and all of the errors were associated with Authentication files and supporting authentication files such as signin.ascx, WindowsSignin.aspx, etc.

To troubleshoot, I did a fresh install of 4.6.2 and the site built without any errors in VWD.  I then compared all the files in the clean 4.6.2 install with the files from my upgraded site and found many files in my upgraded site that were no longer included in the 4.6.2 clean install. Specifically:

AuthenticationSettings.ascx and the associated code behind file
loggoff.aspx and the associated code behind file
signin.ascx and the associated code behind file
WindowsSignin.aspx and the associated code behind file

All these files were located in my admin/security directory in my upgraded site.  As a test, I simply removed the files and the upgraded site built without errors and all normal forms of authentication are working for the site without any problems.

Were these files just leftover from stripping out the AD component and moving it to the provider model?

Also, many of these  AD post make reference to a signin.ascx.vb file for certain tips, tricks, or modifications.  Under the clean install scenario, this file is not there.  Has the name and location changed?

Have I done any harm to present or future functionality by removing the above mentioned files.

Thanks,

Paul

Hi Mike,

In a perfect world, should these files have been removed by the upgrade package? I'm not to comfortable with rogue files floating around in my production install and truthfully, I'm not so intimately aquainted with DNN as to know exactly what files should or should not be there. I only discovered these by trial and error.

 From another post here:

[QUOTE]sconard wrote

It seems by my testing that mikeh is right and it is not possible to have autologin work in mixed mode.  I did however modifiy the httpmodule.authentication authenticationmodule.vb to test for local address prior to redirect

This is from 3.3.5 in the OnAuthenticateRequest sub.

                If (AuthenticationController.GetStatus(_portalSettings.PortalId) = AuthenticationStatus.Undefined) Then  'OrElse (blnWinLogon) Then
                    AuthenticationController.SetStatus(_portalSettings.PortalId, AuthenticationStatus.WinProcess)
                    Dim url As String
                    'mod check if local address*****************************************
                    'this allows for mixed mode with auto login
                    If Not InStr(Left(Request.ServerVariables("remote_addr"), 3), "11.") = 0 Then
                        If Request.ApplicationPath = "/" Then
                            url = "/Admin/Security/WindowsSignin.aspx?tabid=" & _portalSettings.ActiveTab.TabID.ToString
                        Else
                            url = Request.ApplicationPath & "/Admin/Security/WindowsSignin.aspx?tabid=" & _portalSettings.ActiveTab.TabID.ToString
                        End If
                        Response.Redirect(url)
                    ElseIf (Not AuthenticationController.GetStatus(_portalSettings.PortalId) = AuthenticationStatus.WinLogoff) AndAlso blnWinLogoff Then
                        Dim objAuthentication As New AuthenticationController
                        objAuthentication.AuthenticationLogoff()
                    ElseIf (AuthenticationController.GetStatus(_portalSettings.PortalId) = AuthenticationStatus.WinLogoff) AndAlso blnWinLogon Then ' has been logoff before
                        AuthenticationController.SetStatus(_portalSettings.PortalId, AuthenticationStatus.Undefined)
                        Response.Redirect(Request.RawUrl)
                    End If
                    'old dnn code
                    'If Request.ApplicationPath = "/" Then
                    '    url = "/Admin/Security/WindowsSignin.aspx?tabid=" & _portalSettings.ActiveTab.TabID.ToString
                    'Else
                    '    url = Request.ApplicationPath & "/Admin/Security/WindowsSignin.aspx?tabid=" & _portalSettings.ActiveTab.TabID.ToString
                    'End If
                    'Response.Redirect(url)

                    '***********************************************

And a few other quotes from this same thread:

This is not code incorporated into the new provider right? Because of the unknown of the internal IP scheme of the host? I guess I'm still after having Intranet users automatically logged in and external anonymous users not presented with the WindowsSignin prompt.  I know this things been beat to death in the forums here but when I came across this post it looked like a viable solution if I chose to make the above modification to my code.

What file and what code changes would need to be made to the new provider to accomplish the above fix and does this fix indeed overcome the autologin conundrum?

Thanks,

Paul

Are you saying that we could see another quick release after this first release gets out of the tracker? If so, I can be patient and wait for that release Mike.  Judging by the number of post related to this functionality, I think many folks will be very pleased with this added feature to the AD provider.

Once again...thanks for all the hard work. If I can be of any assistance in anyway, please let me know.

Paul