Hi guys... With the help of a few customers I found out what I think is happening, I think the CORE code is checking to see if a standard DNN Account Login module exists on a page before it allows the page to be the actual login page, while this is great as a precaution to make sure users can sign in, it doesn't really work or play friendly with any 3rd party login modulse/custom login components etc...

The 'work around' is to add a standard DNN login module to a page and change the visibility to be displayed to Administrators only, although this is a work around I hope this gets fixed in future DNN versions, just seems to me that this really limits functionality.

-Chad

Correct, here is the cuplrit called by Globals.LoginUrl (also located in Globals.vb) for your custom login tabid.

        Public Function ValidateLoginTabID(ByVal tabId As Integer) As Boolean
            Dim hasAccountModule As Boolean = Null.NullBoolean
            For Each objModule As ModuleInfo In New ModuleController().GetTabModules(tabId).Values
                If objModule.ModuleDefinition.FriendlyName = "Account Login" Then
                    hasAccountModule = True
                    Exit For
                End If
            Next

            Return hasAccountModule
        End Function

As you can see if your modules FriendlyName is not "Account Login" then it will default redirection to the current tab, using the default DNN login control. A simple fix is to just place the default "Account Login" module on the page and set the security to admin only. This will pass this check and redirect to the page successfully.

Cheers
Shea

test

The same thing (kind of...) happens with the profile page.
I was using a third party module for managing the user profile, so I set the User page in the Site settings to a page with the 3rd party module.
However, when you have an incomplete profile, you will not be redirected anymore to the user page, but DNN will directly show the DNN profile page when you try to log in.