We launched our new web site based on DNN a few months ago, initially with a single portal. The application was to be made available to several countries, each in it's own portal, but pretty much sharing the same code base. After satisfying ourselves that all appeared to be working fine, we released a number of additional portals to rollout the application to the other countries.

Now each country has it's own pre-existing user base of user credentials which were automatically imported into DNN on the first login for a user. Now the trouble began.  Naturally there were lots of duplicate user names across all countries, but we were under the understanding that DNN would handle each portal independantly with it's username database unique to that portal.  Well the PortalId is in the userportals table, right.  Well.... no, DNN interfaces to the AspNetSqlMembershipProvider which assigns the ApplicationName = "DotNetNuke" application wide, so usernames are actually shared across the portal, also requiring the password be identical (to facilitate single login to all portals). So no, the usernames must be unique... but we already have an external database of usernames with duplicates!!!

So.... I know I am not alone. Someone must know a solution to this. Is there an easy workaround to the problem, or are we resigned to have to write a custom Membership Provider to support usernames on a portal basis?  Time is of the essence as we are now live, and we have real people out there who can't login as their username is taken by someone else in another portal.  HEEEEEEEEELP!!! 

I am also aware of the document "Enhancing Membership DotNetNuke Roadmap" by Charles Nurse which describes a solution to this problem and also grouping of portals for shared user logins.  Does anyone know how this is progressing, or whether some of these enhancements have made it into DNN 5?