Authorization Manager (AzMan) problem

[Vlad Bezden]

I am using AzMan for User Authorization.

And sometimes I am getting this error:
A required privilege is not held by the client. (Exception from HRESULT:
0x80070522)'

This error happens at:
AzAuthorizationStore azManStore;
azManStore = new AzAuthorizationStoreClass();

// Initialize AuthMan
azManStore.Initialize(0, azManConnectionString, null);

Application is WCF Windows Service, and for each call to the service it
makes call to the AzMan to authorize user if s/he has rights for the method.

Application is running on Window 2003 server SP2.
AzMan storage is used as xml file.

I checked CPU utilization and it is about 1-2% load.

Lately when we started to receive more traffic I started to get more and
more this errors, please help on this.

Thanks a lot.

Sincerely,
Vlad.

[DaveMo]

On May 28, 7:35 am, Vlad Bezden <VladBez...@discussions.microsoft.com>
wrote:

> I am using AzMan for User Authorization.
>
> And sometimes I am getting this error:
> A required privilege is not held by the client. (Exception from HRESULT:
> 0x80070522)'
>

> This errorhappens at:

>                 AzAuthorizationStore azManStore;
>                 azManStore = new AzAuthorizationStoreClass();
>
>                 // Initialize AuthMan
>                 azManStore.Initialize(0, azManConnectionString, null);
>
> Application is WCF Windows Service, and for each call to the service it
> makes call to the AzMan to authorize user if s/he has rights for the method.

> Application is running on Window 2003 server SP2.
> AzMan storage is used as xml file.
>
> I checked CPU utilization and it is about 1-2% load.
>
> Lately when we started to receive more traffic I started to get more and
> more this errors, please help on this.
>
> Thanks a lot.
>
> Sincerely,
> Vlad.

Hello Vlad,

When I read problems like this I typically suspect a problem in your
code rather then AzMan. No offense, but AzMan was probably much more
rigorously tested then your application. But there could be a problem
anyways. I would start with your application, though, and see if you
can set up a stress/test harness that reliably reproduces the problem.
Then start eliminating other pieces of your app and see if the problem
goes away.

Alternatively, why can't you preserve your azManStore between calls to
your web service? This would improve performance and will undoubtedly
make the problem go away.

HTH,
Dave

[Vlad Bezden]

Hi Dave,

Thanks a lot for reply and suggestions. You might be right that AzMan is
well tested, but I am having this problem for last year, and I used different
code (I also copied code from MSDN), and I am still getting the same problem.
Maybe I am doing something wrong, do you have some code that I can look how
you did it and use in my application?

I like your idea about open AzManStore and keep it open, but what I don't
like about it is if I add or delete user, it will not pick changes up, and I
need to restart my service. I think I tried it in a past.

Please advice.
Thanks a lot.

Sincerely,
Vlad.

[Vlad Bezden]

Dave,

Also I recall keeping AzManStore open prevents me to open file from
azman.msc and add or remove users, since it is open for some reason in write
mode. This is known issue, Microsoft promissed to fix it, there were a lot
of complains about that.

Thanks again.

Sincerely,
Vlad.