I'm creating an expense reporting application that will store all information in an SQL database. Currently i'm using Forms authentication with an AD Membership provider and an SQL role provider.
Everything is working fine with authentication and authorization, but I've noticed that the aspnet_users table only populates when you assign a user to a role. This makes sense.However, I'd like some permanent way to relate users to records that they own in my other tables, can I use the aspnet_users GUID to provide this (e.g. use their GUID as a foreign key in some other table so I don't have to create a separate Users table in my application database and somehow keep it synched with AD)?
I'm wondering how safe it is to use the aspnet_users to establish relations? Do the users get cleaned-up if you remove them from all roles? I assume the GUIDs never change, but can I safely create foreign key relationships based on the GUID?
I do ...
Go to the complete details ...