OK Gang... I've been at this for hours (My OCB won't let it go)...
Basically here's what I've witnessed and read:
If you add a user to a portal (username/password: test/password), then go to another portal and try to add the same username, but different password (username/password: test/p2), you get the "invalid username" error (a little cyptic I'd say - username is only "invalid" because it's already being used). If you use the SAME username & password, you have success, but in reality, both users from both portals have 1 record in the DNN Users table, but 2 records in the aspnet_Users table. This *seems* like a bad thing, but I'm not sure what the ramifications are.
It seems like there could be some intentional reason for this, but I can figure out what that would be, and it seems like it would more than likely cause a problem because the DNN code is treating the username/userid as 1 login, but aspnet is treating it like separate logins.
Can anyone straighten me out on this? Is this something that *could* bite me as I move forward with my first DNN install? I have read other threads explaining the exact same confusion/concern, but no "official" word from the DNN folks on whether this is an issue and what the actual ramifications of the issue are.
Any enlightenment would be greatly appreciated.