Azman returns cached roles to .Net API

Hi, I'm using Active Directory as Membership Provider and Azman as
RoleProvider, everything works fine except that any change made in Azman
after the ASP.NET 2.0 APP is
initialized returns a cached version of the roles information. The APP needs
to know about any change produced while is running. Any idea why Azman is
returning a cache version of the roles definitions.Thanks.


.

Relevant Pages

  • AzMan vs other approaches for .Net app security?
    ... I'm developing a new .Net 2.0 app for one of my corporate clients. ... I've done for them in the past is provide role-based security in their VB6 ... It's been about two years since I read about AzMan, ... user role membership stored in the app's database and checked by the app ...
    (microsoft.public.dotnet.security)
  • RE: AzMan concurrency.
    ... I need to implement an application with load balancing support; ... For the authorization part of the app, I was planning to use AzMan. ... AzMan seemed to be the perfect solution; the store (when in Active ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Understanding MMC and AzMan
    ... I do understand that my app might have specific needs, ... you just create an operation/task (really ... the snap-in to your specific needs for any application. ... I'm suprised there's been nothing before like AzMan that provides ...
    (microsoft.public.platformsdk.security)
  • Re: AzMan concurrency.
    ... Web client sends message (with a correleationID) to specific MSMQ ... NT Service listens on that QueueA and updates AzMan store according to ... > For the authorization part of the app, I was planning to use AzMan. ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Azman returns cached roles to .Net API
    ... > RoleProvider, everything works fine except that any change made in Azman ... > initialized returns a cached version of the roles information. ... The APP ...
    (microsoft.public.dotnet.framework.aspnet.security)