Architecture

Re: Object Oriented way to handle access

vivek_iit — Fri, 03 Jul 2009 13:34:10 GMT

piyushc:
Depending on the user role, I need to show/hide some part of the page and even set properties of the controls.

This has led to n number of if-else statements in my aspx page which does not smell good.

You need to create a Permissions utility class, with a method like : bool HasAccess(ActionEnum action, User user)

You can divide your system objects into Actions, like ShowHeader, ShowFooter etc.

Each user will have its own permission set, and this utility function will check the user's role and associate it with the relevant permission to return true or false based on if the user has permission to perform that action or not.

Hope this helps,

Vivek

Re: Object Oriented way to handle access

DigiMortal — Fri, 03 Jul 2009 13:06:47 GMT

I think that it is bes for you if you separate the pages for different roles. User controls should be able to function without knowing who and how is using them - they just get their data and get all the orders from parent controls or pages. Maybe today your code behind the pages is not very large and complex to handle but it may happen soon. Usually all specific roles add their own little differences and it is better if you consider this right now than later when there is a lot of code that needs to be moved and refactored.

Re: Object Oriented way to handle access

v.vivek — Fri, 03 Jul 2009 09:40:46 GMT

this are my sugession that may be useful for ur application.

create usercontrol (Nevigation control) on the basis of different role.

on login store role type in session .

dynamic bind specfic usecontrol based on role.

Re: Object Oriented way to handle access

RickNZ — Fri, 03 Jul 2009 08:52:09 GMT

The ideal object oriented way is that each object knows how to display itself, including in response to the current role, etc.

You might consider things like creating some user controls that know how to respond to the current role. If the actions involve multiple pages, you might be able to implement some of the logic in a master page or in a common page base class. If it involves all controls of a given type, you can use control adapters or tag mapping.

Object Oriented way to handle access

piyushc — Fri, 03 Jul 2009 06:43:30 GMT

Hello All,

I have this question since quite some time now.

I have a project in which I have few user roles.

Depending on the user role, I need to show/hide some part of the page and even set properties of the controls.

This has led to n number of if-else statements in my aspx page which does not smell good.

What is the way to handle such scenarios using Object Oriented techniques?

Help is appreciated.

Thanks, Piyush