Membership Provider and Permissions
-
Hi Guys, I'd like to make a blog / forum web app as research, and i'd like to use the (Sql)MembershipProvider to manage my users, but i'd like to tie Permission information to them. I had a few ideas, but wondered what the standard was - 1) Add a permission indicator to the Comment field Thoughts: Cheesy as hell, not particularly scaleable or searchable. 2) Create a seperate database and create both users at the same time. Thoughts: Seems nice on the surface, but i would be maintaining two databases, one with login credentials, and one with the user and additional data. 3) Extend the existing SQLMembershipProvider database to support permissions, and expand the "User" object to include permission level. Thoughts: Work, maintainability, and sabotaging something that already works. Plus, i would have to integrate both the DB's above, into a single entity. Doesn't scale well with the a permissions table either. 4) Seperate databases, like option 2, only with a Permissions table. Thoughts: Heavy work, i'd need to do some more research into permission sets, but I suspect this is probably how things are done at the moment. Hope you guys can shed some light on this. Regards Tristan Rhodes
------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
Hi Guys, I'd like to make a blog / forum web app as research, and i'd like to use the (Sql)MembershipProvider to manage my users, but i'd like to tie Permission information to them. I had a few ideas, but wondered what the standard was - 1) Add a permission indicator to the Comment field Thoughts: Cheesy as hell, not particularly scaleable or searchable. 2) Create a seperate database and create both users at the same time. Thoughts: Seems nice on the surface, but i would be maintaining two databases, one with login credentials, and one with the user and additional data. 3) Extend the existing SQLMembershipProvider database to support permissions, and expand the "User" object to include permission level. Thoughts: Work, maintainability, and sabotaging something that already works. Plus, i would have to integrate both the DB's above, into a single entity. Doesn't scale well with the a permissions table either. 4) Seperate databases, like option 2, only with a Permissions table. Thoughts: Heavy work, i'd need to do some more research into permission sets, but I suspect this is probably how things are done at the moment. Hope you guys can shed some light on this. Regards Tristan Rhodes
------------------------------- Carrier Bags - 21st Century Tumbleweed.
This sounds like a job for the RoleProvider. This link might give you some ideas: http://www.odetocode.com/Articles/427.aspx[^]
Deja View - the feeling that you've seen this post before.
-
This sounds like a job for the RoleProvider. This link might give you some ideas: http://www.odetocode.com/Articles/427.aspx[^]
Deja View - the feeling that you've seen this post before.
Awesome - Didn't even know it existed :) Thanks. Tris
------------------------------- Carrier Bags - 21st Century Tumbleweed.
-
Awesome - Didn't even know it existed :) Thanks. Tris
------------------------------- Carrier Bags - 21st Century Tumbleweed.
No bother - we're here to help.:-D
Deja View - the feeling that you've seen this post before.