I am working on a web application that will use AD for authentication but use SQL Server for both roles and profile data.
I intend to use the SqlRoleProvider and a custom Profile Provider (once I can get it working in a web project).
Really I just wanted some opinions on my implementation and whether or not it is best practice - below is test app.
Whilst many new properties will be stored using the custom provider, I still need to access some of the properties in active directory (email address, other contact details etc.).
I create a user class that will be used as a wrapper for both AD properties and other custom properties:
public class TestUser
{
#region Ctor
public TestUser()
{
}
#endregion
#region Properties
// properties from AD
public string UserName { get; set; }
public DateTime LastUpda ...
Go to the complete details ...