Task Authorization versus Operation Authorization

May 16, 2009 at 4:33 AM

First off, thanks for writing something like this.  I think it will prove to be invaluable for a lot of projects, big and small.

I'll be implementing this as my primary Role Provider in a new ASP.NET MVC project.  So far, it is working as expected except for one thing.

If I add operations to a task, and then add the task to a role, when I checkAccess for an Operation in that Task I get Deny back as the Authorization.  Now if I add the Operation to the Role directly, the Authorization comes back as Allow, which is expected.

Am I configuring this correctly or not?  I would assume if an Operation is contained within a Task, then the Role should be granted Permission to any operation in the Task, right?


David Hollins


May 16, 2009 at 5:18 AM

Please disregard, the problem was some logic in a business rule on the operation I was calling.

Things are working perfectly!

May 16, 2009 at 8:46 AM
You scared me. :-)