By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,050 Members | 1,564 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,050 IT Pros & Developers. It's quick & easy.

App level security w/multiple roles

P: n/a
All,

I have some questions about a possible solution to my scenario. Here it
is.

A person can belong to multiple applications
A person within an application can have multiple roles
A role within an application can have access to different
navigation(pages)

How can I prevent redundant navigational elements from showing? I use a
distinct filter to prevent duplicates but for some reason i get an
uneasy feeling about this method. Since a person can have multiple
roles..a single page will be used where different access will be
applied. Example, widget.aspx will check your roles and display certain
items via the code behind.

Here are a couple of queries to pull the information.

http://www.teewebco.com/images/all.gif
http://www.teewebco.com/images/distinct.gif

Should I use impersonation to accomplish this since I would be able to
keep the pages unique to the role and they user can switch in and out
of the the roles to accomplish this?

Sep 21 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hello tm******@teewebco.com,

What do u mean with "How can I prevent redundant navigational elements from
showing"?
Do u want to hide elements where user have no righs?

You should assign specific tag/activity for each element/page. Then in database
map you role to these activities/id and in you code check whether user can
see this or not
All,

I have some questions about a possible solution to my scenario. Here
it is.

A person can belong to multiple applications
A person within an application can have multiple roles
A role within an application can have access to different
navigation(pages)
How can I prevent redundant navigational elements from showing? I use
a distinct filter to prevent duplicates but for some reason i get an
uneasy feeling about this method. Since a person can have multiple
roles..a single page will be used where different access will be
applied. Example, widget.aspx will check your roles and display
certain items via the code behind.

Here are a couple of queries to pull the information.

http://www.teewebco.com/images/all.gif
http://www.teewebco.com/images/distinct.gif
Should I use impersonation to accomplish this since I would be able to
keep the pages unique to the role and they user can switch in and out
of the the roles to accomplish this?
---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
Sep 21 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.