WE have just launched our live web site which has multiple portals, each portal representing a different country using the same web application.  The usernames for each country are meant to be unique, but it appears that now we have gone live, the usernames are shared across portals.

I have now researched this extensively, and it appears as if this is by design, as DNN Uses the AspNetSqlMembershipProvider and unlike earlier versions of DNN, now use the same application name = "DotNetNuke" rather than the PortalID for each username. A username can therefore be shared across portals if the passwords match.  If the passwords do not match when you attempt to register on a 2nd portal, you are told the username already exists.

Well now I'm in a serious situation as we are live and uers cannot login (we intercept the login and transfer profile settings to DNN from an external database on first login) as the duplicate usernames in different portals are being rejected by DNN as explained above.  Is there any way to allow this to occur in DNN 4.9.0?  Is the new membership functionality being released in DNN 5.0 as per the "Enhancing Membership DotNetNuke Readmap" by Charles Nurse, dated June 21 2006?  If not, does anyone know of a custom membership provider that solves my problem?

HEEEEEEP!