Operating System: All
Platform: All

I will attempt to clarify this.

AuthZ decisions are currently made based on URL/Role/DOM operation. This is hard coded and the real use case that AAA AuthZ attempts to support (RBAC).

What Ajay is asking for is essentially a hook into the AuthZ engine to allow the AuthZ decision to be made using different criteria.

For transparency, in a conversation with Ajay offline we discussed two different approaches to support such behavior:
1) Provide callback hooks in the AuthZ engine and an interface to make more advanced AuthZ decisions.
2) Extending the DomDataBroker or AuthzDomDataBroker. I would suggest extending the latter, since then you can invoke super methods to make basic AuthZ decisions.

The idea is to allow other groups/projects/individuals the capability to "gate" DOM transactions based on their own criteria.

This will be added to the list of Boron priorities. This is a new feature request, and could be considered during the next release if resources are available.