When I create my own login control (to utilize a custom Authentication Provider), dropping it on a page and listing that page as the Portal Login Page causes an error. The nature of the error is that the Portal is looking for a login page to implement a module with a specific FriendlyName ('Account Login').
The way I get around this is I created a query that goes into the DB and changes the Friendly Name of the built in DNN Account Login Module to something different, and then give my module a FriendlyName = 'Account Login'.

That said, I am afraid that future upgrades will overwrite my changes and my site may stop working.

Can you comment on how safe this is to do, or suggest another course of action?

Thanks!

Hello,

Well you can just make your own log-in provider. Then, you can disable DNN's provider and only enable yours - that accomplishes this.

I created my own authentication provider for our system... the help wasn't great, but I just looked at the source code from the default one and you can go from there.

Hope this helps,

Mike