Hello,

I remember reading about this a while ago but I can't find the posts-

Bascially I have a couple of users with the same username on different Portals (SSO I suppose, but unwanted). This means that when my UserProfile queries data by UserID (it does not use PortalID) - the same information is displayed in both sites.

For example, on PokerDIY, my username is "rod", but this is my username in other portals, and it's sharing information. I want to detach the user and have to separate users in each portal - if I unregister the user on PokerDIY I am worried it will delete the user in the other portal too (otherwise I would just delete that user from PokerDIY and make a new user.

I run 2 sites on the same DB. They are from the old DNN 2.x versions, and I think somewhere a long the line this problem has crept in.

Has anyone experienced this and is there a script that can detach the users? They have different data in the asp_net membership tables (ie. email is different) - it is the stuff in the Users table that is duplicated, so I guess I need to make a new record here and update half the records in the asp_net tables to point at that one for PokerDIY.

Any comments?

---

Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

The only way to "separate" tem is to create different users, i.e. with different usernames. In your case there is only one user "Rod" who has membership of 2 portals.

If you have the latest version of DNN I am 90% sure you can safely delete Rod from one portal and it won't affect him in the other one. In older versions of DNN, deleting Rod from one portal would delete everything about the user, i.e. he would be deleted from both portals.

This issue caused me great concern. Especially becuase two user (though highly unlikely) could end up with shared membership accounts. There was an old thread about it at http://forums.asp.net/thread/1015536.aspx.

I put in some code in the user sign in process to prevent this from happening on my sites. I'll dig up and post the fix in a bit. Sorry, I never had to seperate accounts in production. My one portal that had issues with linked accounts only had a handful of users, so I just started it over.

 

---