| Authorizations define what a user
can do in an application: Basically, you define what the user
is allowed to see, do and modify in your applications based
on his role. Specific words are used to define authorization:
Permissions, Rights, Restrictions, Privileges….
There are two ways of defining authorizations:
The most secure way is to forbid everything by default,
and then grant permissions to allow possibilities. This
way, if you forget to define a permission, the user won’t
be able to do something he should, rather than accidentally
do something he shouldn’t.
The faster way is to allow everything by default, and then
you assign restrictions to forbid some actions. This way
is faster because typically there are fewer restrictions
than permissions.
But as a result you usually end up with a role based access
solution that is complex, costly to maintain and difficult
to update.
|
Request a trial version of Visual Guard!
Re-use AD accounts for .Net authentication