Re: How many roles is too many?
- From: "Joe Kaplan \(MVP - ADSI\)" <joseph.e.kaplan@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 18 Jun 2006 09:41:51 -0500
You might want to check out a framework like AzMan. It allows you to map
high level application roles to lower level tasks and operations. Perhaps
the permissions in your app could be represented by operations and groups of
them might roll up into higher level concepts?
Joe K.
--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
<Warm.Beer@xxxxxxxxx> wrote in message
news:1150331787.809031.295620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the prompt replies, guys.
I have definitely been turned off storing this amount of relately
static data in the client cookie.
The number and granularity of the permissions set is a business
requirement, so we can't easily remove any flexibility currently used
by our customers. BTW, it's ~1000 users per installation, not total
(my bad!)
I've had a bit of a look into the Membership/Role providers in 2.0, so
will probably proceed down that path, as it gives enough flexibility
without a lot of code.
Cheers,
Brett
.
- References:
- How many roles is too many?
- From: Warm . Beer
- Re: How many roles is too many?
- From: Warm . Beer
- How many roles is too many?
- Prev by Date: Re: Asp.net & Ssl
- Next by Date: Re: persisting credentials across different sites running .net 1.1 and 2.0.
- Previous by thread: Re: How many roles is too many?
- Next by thread: making a report of upload file
- Index(es):
Relevant Pages
|
|