Re: Question about Authorization Manager

John wrote:
Secondly to this.. why is it that a task that has only a lower level task as its definition considered invalid? (throws an exception) It seems to me that the operations as defined are supposed to be low level operations, I should be capable of creating a single task from the definition of two or more tasks that have their own operations. Yet this as well throws an exception.

Ok.. sorry to keep replying to myself.. but I discovered why the above is happening. This doesn't explain my original question because that behavior I believe is within AzMan itself.

I located the code that is generating an error based on a Task that is only comprised of lower level tasks. It is within Security Application Block file AzManAuthorizationProvider.cs line 166-169

if (operations.Count == 0)
{
throw new ConfigurationException(SR.NoOperations);
}
.

Relevant Pages

  • Re: Question about Authorization Manager
    ... as its definition considered invalid? ... as well throws an exception. ... underlying AzMan level, its the only securable for which your application ... can request access permissions. ...
    (microsoft.public.dotnet.security)
  • Re: Question about Authorization Manager
    ... why is it that a task that has only a lower level task as its definition considered invalid? ... Yet this as well throws an exception. ... None of this makes sense considering the documentation within Authorization Manager. ...
    (microsoft.public.dotnet.security)