Re: Need to create in-memory store for authorization roles

From: bruce barker (nospam_brubar_at_safeco.com)
Date: 08/12/04


Date: Thu, 12 Aug 2004 09:16:54 -0700

you can cache them in the application object are just create a static
hashtable. you will need to sync access.

-- bruce (sqlwork.com)

"Bill Borg" <BillBorg@discussions.microsoft.com> wrote in message
news:523F2D23-2F1E-4F3D-9A92-A83649B0271E@microsoft.com...
> Hello,
>
> I want to build user roles during AuthenticateRequest for use during
> authorization. I know I can go get the roles from the database and add
them
> to the principal, but would like to cache the roles in memory rather than
> always go to the database. I'd like to use the equivalent of the session,
but
> know that at the point where I need this the session state bag is not yet
> reestablished.
>
> Any thoughts on how best to create an in-memory store for user roles?
>
> Thanks,
>
> Bill Borg



Relevant Pages

  • Need to create in-memory store for authorization roles
    ... authorization. ... I know I can go get the roles from the database and add them ... know that at the point where I need this the session state bag is not yet ... Any thoughts on how best to create an in-memory store for user roles? ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Error 21002: [ SQL-DMO] User "xxxxx" already exists.
    ... you can drop the user from the database using ... > Can you please let me know how to resolve this. ... > then it is still visible under different user roles ... It does not delete the user account from ...
    (microsoft.public.sqlserver.security)
  • plz-help enumeration database objects that users roles have ?
    ... I I just inhertied a database that I am trying to document. ... I have many user roles and users under this database. ... so I am wondering if smbdy has any suggestion or some sql code that hits the ... map or definition for them so I am pretty relunctant on diving in it? ...
    (microsoft.public.sqlserver.security)
  • Re: Error 21002: [ SQL-DMO] User "xxxxx" already exists.
    ... No restoration of database was performed. ... I do not see that user account as orphaned. ... >> then it is still visible under different user roles ...
    (microsoft.public.sqlserver.security)