Mike Horton wrote:
Easy depends on your perspective. 
Is there an order selector in the DNN interface? No there isn't but if you open your database, go into the Authentication table, and change the PackageID for DNN so that it's higher than the Active Directory PackageID it'll then be listed as second.
As for you section question: It's because the Login wrapper is a Tab control so all the controls are loaded and as you switch between them they become visible (everything between the Login selection buttons and Register (or Remember Login) belongs to the individual authentication providers). Because the Standard Login button grabs the focus when the page is loaded it cancels out the AD provider's attempt to capture the focus. You'll find that after you switch the order as per the above that the event will fire as you expect it to on Windows Login but won't anymore on the Standard DNN control.
Just tried out your tip on our testing environment, which is on DNN 5.2.3 (as that's our current production version too). Doesn't work. However, if I use your tip on the primary key, thus the AuthenticationID-field, it does. But, to change the AuthenticationID-field, you have to first alter the field itself to not auto-increment, then make the changes, and put it back to auto-incrementing again.
So yes, it seems to be working, but it's just another hack that's most probably not officially supported by DNN and thus there's always the risk that it suddenly stops working in a future version, and then we're back at the starting point, out to find another hack to fix it again, goto loop.
In any good applications administrators perspective, using dirty hacks should only be a fallback-solution; thus be used only if strictly necessary.
Are there any plans yet, to make DNN support ordering the authentication tabs natively? It should really be a simple task and by putting in the effort to add it to DNN I think you'd make a lot of DNN-users even happyer than they already are!
I'd be happy to coöperate in developing the feature, in order to support DNN that way. I think my employer would agree to that too ;)