Restricting access to records. Is claim-based permissions a good idea.
Posted
by Vitalik
on Stack Overflow
See other posts from Stack Overflow
or by Vitalik
Published on 2010-06-05T03:33:18Z
Indexed on
2010/06/06
18:12 UTC
Read the original article
Hit count: 223
in .net Claim-based identity framework
If i wanted to restrict users to do an operation (view or edit) on let's say an account, a particular account #123456.(i am talking about business entity, like a bank account.) Is it a good idea to create a claim for each account they can view or edit?
Any disadvantages of having a lot of claims in a set? a system admin might have access to all accounts in the system thus creating hundreds of claims (maybe more than one for each account)
© Stack Overflow or respective owner