ASP.Net membership and Roles Managment -
ASP.Net 2.0 is looking for some feedback built in subscription and role management.
Do many people use it? What's good and / or bad about it? Can I assign multiple roles to a single user? What is the optional standard for Net Apps?
Personally considering the permissions or actions defined for a role, it seems that I could only play a single role and I would like to have roles to get permission from each other. It was a great headache to manage the team created in the membership manager.
If I am the light ... ..
Publisher Editor's Member
And I want the editor to have some permissions, which have something with the publisher and the member , It would be difficult in my code to determine whether the current user can edit something rather than just a list of permissions drawn by a role and just to see if the "edit paragraph" is in the list .
Using built-in subscription providers is very easy, and it is quite secure. I have used many versions of it in different projects. The great thing about it is that if it does not do exactly what you need to do then you can always increase it, there are roles in the underlying identity object, they are easy You can access, store, compare.
If you are using Net and you need a fast, pre-packaged, reasonable secure authentication source, then you are in fact wrong with the built-in subscription provider. If you need more security, just take those who give you and make it a bit more hard-core. If you have an LDAP store, then the existing subscription certification is quite easy to integrate.
Comments
Post a Comment