Re: Listing domain users
- From: "MikeS" <michael.spencer@xxxxxxxxx>
- Date: 20 Feb 2006 12:24:08 -0800
The simple answer may be that you may need to use of a rolemanager and
make use of calls to User.IsInRole to determine what you will allow
your users see and do.
I wonder about some other things...
Are you using the WindowsTokenRoleProvider, that is, are the roles you
mentioned defined as NT groups?
Do you have your sql procs locked down with grants based on these same
roles so that you need to impersonate the callers role back to the
database? If so you may want to use different connection strings based
on each type of user. ...Or is there a (nother can of worms) middle
tier...
Me, I think it is probably more trouble to manage different views in a
single page than to just create the three pages that know exactly who
they are dealing with and isolate as much common functionality using
web controls and master pages. But otherwise maybe look at the
multiview control.
Note that location tag lock downs using windows auth and NT group names
don't need a full blown rolemanger but as soon as you want to call any
Roles.* method or anything like it you need the rolemanager.
.
- Follow-Ups:
- Re: Listing domain users
- From: Joe Kaplan \(MVP - ADSI\)
- Re: Listing domain users
- References:
- Listing domain users
- From: Felix_WafyTech
- Re: Listing domain users
- From: MikeS
- Re: Listing domain users
- From: Luke Zhang [MSFT]
- Re: Listing domain users
- From: Felix_WafyTech
- Re: Listing domain users
- From: Joe Kaplan \(MVP - ADSI\)
- Re: Listing domain users
- From: Felix
- Listing domain users
- Prev by Date: Re: Listing domain users
- Next by Date: Re: Listing domain users
- Previous by thread: Re: Listing domain users
- Next by thread: Re: Listing domain users
- Index(es):