I need to authenticate against a SQL Server of another application.
I used an exact copy of the DNN membership provider source (with altered namespaces and file names) and implemented it in DNN.
Of course, using this one instead with the default connection, causes no problem at all as expected.

However, I want to use multiple membership providers. Is this possible??
In my web.config file, I have the following nodes:

<members defaultProvider="myCustomProvider">
      <providers>
        <clear />
        <add name="myCustomProvider" type="Dnn.Membership.Provider.myCustomProvider,myCustomProvider" providerPath="~\Providers\MembershipProviders\myCustomProvider\" />
        <add name="AspNetMembershipProvider" type="DotNetNuke.Security.Membership.AspNetMembershipProvider, DotNetNuke.Provider.AspNetProvider" providerPath="~\Providers\MembershipProviders\AspNetMembershipProvider\" />
      </providers>
    </members>

To my understanding, by specifying a 'default' provider I assume that at some point I will be using some other than the default one.
I even made a copy of the Login.asx files (as an alternative authentication) and I pass a 'MyProvider' variable as authType.

How can I make this work and have 'Standard Login tab' to authenticate in the default DNN database and 'My Login Tab' authenticate in another database?\
Has anyone implemented the use of multiple membership providers, and use them as required at runtime?