MembershipProvider, IPrincipal, IIdentity?

Posted by MRFerocius on Stack Overflow See other posts from Stack Overflow or by MRFerocius
Published on 2010-03-24T20:04:08Z Indexed on 2010/03/29 11:53 UTC
Read the original article Hit count: 513

Hello guys;

I have a conceptual question... I am making an Intranet application (Web platform) for a company. I have a SQL Server DB with these tables:

Users (userID, userName, userPass, roleID)
Roles (roleID, roleName)
Pages (pageID, pageURL)
RolesXPages(pageID, roleID)

How is the best way to create a structure to store all this information while the user navigates the site, I mean, on the thread I should be able to check his role, his pages (the ones he can access) I have been reading and there is a lot of stuff there where Im confused, I saw the MembershipProvider, IPrincipal, IIdentity, etc classes but Im not sure what should be the best one for me.

Any thoughts...

Thanks in advance!

Edit: Everytime gets more confusing... I just want to handle those structures at runtime and be able to mantain state during page callbacks or changing pages...

© Stack Overflow or respective owner

Related posts about security

Related posts about ASP.NET