I want to implement a single user sign on system for several web applications using the membership provider in asp.net 2.0 but having examined the schema of the generated schema for the database I have found a problem.
The primary key in the aspnet_users table is user_id as it is in the aspnet_membership table. This makes it difficult for a user to use the same login for several applications.
I know it is possible to apply the same application name to the web.config file in several sites so that the user list applies across applications. The only problem with this is that my different applications require different roles and profile settings and I would end up with all the roles and profiles appling to all web applications which could get messy.
Is there any way round this without altering the schema and consequently the provider classes?
Did you find a solution yet? I ran into the same problem ....