https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/AAA-59 aaa <p>AAA AuthZ should allow other components to register callbacks for providing authorization decisions on requests made.</p> <p>Operating System: All<br/> Platform: All</p> AAA-59

Allow applications to register themselves for additional AuthZ operations

Improvement Confirmed Unresolved Unassigned Ajay L Wed, 19 Aug 2015 20:42:57 +0000 Thu, 21 Mar 2019 11:56:42 +0000 General 0 1 <p>I will attempt to clarify this.</p> <p>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).</p> <p>What Ajay is asking for is essentially a hook into the AuthZ engine to allow the AuthZ decision to be made using different criteria.</p> <p>For transparency, in a conversation with Ajay offline we discussed two different approaches to support such behavior:<br/> 1) Provide callback hooks in the AuthZ engine and an interface to make more advanced AuthZ decisions.<br/> 2) Extending the DomDataBroker or AuthzDomDataBroker. I would suggest extending the latter, since then you can invoke super methods to make basic AuthZ decisions.</p> <p>The idea is to allow other groups/projects/individuals the capability to "gate" DOM transactions based on their own criteria.</p> <p>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.</p> Development External issue ID 4159 External issue URL Rank 0|i023uf: