So i just fired up a second AS portal on one installation, worked perfect. Since it is a separate portal, i registered as "drew". AS happily took my registration, happily hooked my registration for a new "drew" and merged it with my old "drew" from another AS portal, displayed my status message from the other portal and overwrote my eddress.

Active Social didn't do any of this, DotNetNuke did. That is the way it handles users across portals. I would suggest using a different user names on multiple portals.

So did any of the geniuses at DNN Headquarters ever envision that two portals might not have a central phone line where all the users could get on a community phone chat and ask who has used which username? Sometimes i shake my head and wonder where all the brain cells go. Seriously? Absolutely what purpose is a user defined higher than a portal ever going to serve a system that generates a portal as it's base product?

So now, with an empty AS site, as soon as somebody registers with "Bob" in portal B, suddenly Bob over in Portal A has an intruder in his account.

This sucks. Surely i am missing something. I walked the dnn pages and see no intelligent way to say, "hey dnn, guess what? i have two portals and they don't all hold hands and ask who has what username.

I am not very happy to have to go out and buy a second license to run a second AS site on a licence i bought that is clearly shown to be multi-portal friendly.

No. This only happens if Bob registers on Portal B with the same user name, password and email address.

Drew,
What about setting RequiresUniqueEmail in web.config to true.

On Edit
There are some risks associated with enabling this on an established portal

http://www.smart-thinker.com/DNNBlo...fault.aspx

hey Steve, thanks, that would already be an issue (uniqueness for eddresses) as i know there are a bunch (me being one of them).

But riddle me this: if all this single-user/multi-portal scenario is tweaked/tested/groovy: why did my verification email for Portal B get sent to my inbox on Portal A? It never even arrived in my real inbox, meaning my true email inbox. I had to go and use the login page on Portal B to verify my account. This makes little sense. I have not been happy with the evolution of the hierarchy of dnn user structures and this just further compounds that feeling.

How about a reduced license, say $10 per extra portal to get around this?

scratch that last issue, SORT OF.. i just went to my brand new portal, to my brand new account and low and behold ALL my email from the other portal is there in the AS inbox.

Didn't anyone bother to test this? Is there not simply portal id filtering in play? Surely there must be if the userid is site-wide? This is not critical at the moment as the site is new, but it is troubling.

Its not a brand new account. You linked your original account to the new portal. Again, if you don't like this behavior then don't register with the same username and password on child portals. This isn't anything new to DotNetNuke, it has been this way since the beginning.

i beg to differ. This is a new AS portal. This *is* a new account. Explain why all my Portal A email is being shown in Portal B? How does this make any sense?

Did you create your "new" account with the same username and password that you use on the first portal?

i already said i did.. look at this from another non-dev perspective: two websites, two community sites, you registrations. Are you suggesting that we as price-conscious developers are wrong in trying to use the same dnn install to service to small- to medium- size sites and ask us to go and respond to tickets asking why email from one site is showing up in another just because the user, like 99% of the world, will create accounts with the same name and password?

Fine, for now i will go and wipe the account.. no wait, we can't do that without walking through the myriad of dnn user tables as dnn doesn't hard delete any longer.

Fine.. i will just go away create another account with yet another password. Clearly logic is not part of this equation.

Posted By Will Morgenweck on 10 Feb 2011 09:57 AM

So now, with an empty AS site, as soon as somebody registers with "Bob" in portal B, suddenly Bob over in Portal A has an intruder in his account.

No. This only happens if Bob registers on Portal B with the same user name, password and email address.

I wanted to ensure it is noted that as mentioned earlier: i used a different eddress. This new eddress *replaced* the one that was from my registration at portal A.  So it did a simple lookup for my username and password then proceeded to overwrite that account. This is not good record management. Disagree if you like because that is the way it is, but it doesn't make it right, it simply makes it "by design" in the current bits. I don't dare try and delete the portal B account lest it affect my other portal.

It isn't for me to agree or disagree, it is the way it has always been handled in DotNetNuke and not something we have the ability to change.

i understand Will, i do. But again, answer this: why is portal B showing portal A email? Like i asked: surely there is a portal id filtering going on? Would it help to show a screenshot of the two site inboxes side-by-side?

We will look into messaging. Most filtering is done by Portal Id + UserId.

Posted By Will Morgenweck on 11 Feb 2011 12:29 PM

i understand Will, i do. But again, answer this: why is portal B showing portal A email? Like i asked: surely there is a portal id filtering going on? Would it help to show a screenshot of the two site inboxes side-by-side?

We will look into messaging. Most filtering is done by Portal Id + UserId.

thanks.. and just for clarity, here is a screensnap, where you can note the different account profile pics along the repeated emails.

After a night's sleep, and after a really crappy day yesterday (finally got my dog's ashes from the vet), and trying to face the world without my beloved pooch at my side, i have had a few hours to consider my two portals and the absurd reality that when i post in one how that status shows in the profile of the other. Clearly there are areas where the portal id is not being used as a filter.

I consider this a major issue. I also consider this likely fairly easy to fix as there are already structures in place that are filtering, so the addition of the portal id should not be hard. Perhaps a few sql changes to ensure the portal id is part of the joins. But.. this is likely an fairly quick hot fix. As i have already been promoting portal b from portal a, and i KNOW new users will sign in with the same credentials, there will be pie on my face soon. I am not asking people to use a different combination to register, this is not a valid option, i hope you understand my perspective on this.

Interesting, i just watched an episode of Monk (season 7) where an entire case was based on a person's desire to use the same credentials. Crap, i don't even like asking users to use a certain minimum number of characters in the passwords, it seems intrusive.

and another area of concern, needing filtering: see this image for reference. This is the display of ALL members in my new AS portal:

to add to this issue: now i get two emails for every one that i receive into either portal.