Hi to all,

following scenario:

- create portal one (e.g. the root portal during installation), define the admin account with the user name "admin"

- create portal two, define the admin account with the user name "admin"

imagine, how i was surprised to login to the root portal (portal one) with the admin account informations of portal two!

The quick look into the database "Users" offered the definition of the user name as unique. The second look offered, that "admin" of portal two was mapped as user in portal one and two.

I am just imagining, how surprised a customer admin will be, if he defines some users and gets user account informations of users of other portals!?

What i was expecting is an error message, if a user is already existing. Another possibility is the uniqueness of username and portalid (may be mapped as technical key).

Am i wrong? Which documentation should i read? What can I do to prevent this behaviour?

I did use the standard configuration using the "AspNetSqlMembershipProvider".

Thanks,

McShorty

Hi achooyeah,

thanks for your reply.

I have to think about the above described behaviour, if i like it - the possibility to get one matching user/pwd is not really high. I would prefer a uniqueness of user and portal, because the portals are logical independend. Because i didn't read something about this i was surprised.

You mentioned that a search across the site would bring some result. Could you give me a tip which keywords to use?

Thanks,

McShorty