"Pattern" or "best practice" in security checks

[Anders K. Jacobsen [DK]]

Hi

Im developing an ASP.NET CRUD application where i need to do some
authorization checks on surden actions. Eg. some account have access to
delete in a sudden datagrid and some have not. So I have to be more detailed
that on page level. Rather component level.

This ends up, as I see now, in a alot of checks in the different involed
events. Further I have to adjust the view so that actually can't delete in a
sudden datagrid. This is of course not secure enough so therefore the checks
in the events.

This just sounds like a plain nightmare to maintain and develope. Do you
have a clever suggestion to this issue? I guess it's not the first time this
have come up.

To summerize. I want to avoid this.

private void datagrid_DeleteCommand(object source, DataGridCommandEventArgs
e)
{
if(User.IsInRole("Admin") || User.IsInRole("Developer"))
{
long currentid = Int64.Parse(((Label)e.Item.FindControl("lblid")).T ext);
_Service.DeleteItem(currentid);
Databind_datagrid();
}
}

Thanks in regards
Anders, Denmark

[Johann MacDonagh]

I would create a simple permission manager with an XML or database store.
You could simply call something like this:

PermissionManager.HasPermission("Delete", theRowsID);

and it would return a bool stating whether the current user has the
permission to delete that current object. I would then take advantage of the
ItemCreated event of the DataGrid and hide the Delete LinkButton for any
rows that the current user shouldn't be able to delete. You'll still need
code in the DeleteCommand like you posted, only you could use a
PermissionManager setup for easier management.

Here's an example PermissionManager, although it is developed for the .NET
2.0 framework:
http://www.gotdotnet.com/Community/W...0-4655e1a7682b

Hope this helps,
Johann MacDonagh

"Anders K. Jacobsen [DK]" <no**@at.all> wrote in message
news:u1**************@TK2MSFTNGP11.phx.gbl...

Hi

Im developing an ASP.NET CRUD application where i need to do some
authorization checks on surden actions. Eg. some account have access to
delete in a sudden datagrid and some have not. So I have to be more
detailed
that on page level. Rather component level.

This ends up, as I see now, in a alot of checks in the different involed
events. Further I have to adjust the view so that actually can't delete in
a
sudden datagrid. This is of course not secure enough so therefore the
checks
in the events.

This just sounds like a plain nightmare to maintain and develope. Do you
have a clever suggestion to this issue? I guess it's not the first time
this
have come up.

To summerize. I want to avoid this.

private void datagrid_DeleteCommand(object source,
DataGridCommandEventArgs
e)
{
if(User.IsInRole("Admin") || User.IsInRole("Developer"))
{
long currentid =
Int64.Parse(((Label)e.Item.FindControl("lblid")).T ext);
_Service.DeleteItem(currentid);
Databind_datagrid();
}
}

Thanks in regards
Anders, Denmark