https://www.infra-repository.org/oiar/index.php?action=history&feed=atom&title=GF.Permission_Register 2026-05-03T11:18:22Z Revision history for this page on the wiki MediaWiki 1.40.0 https://www.infra-repository.org/oiar/index.php?title=GF.Permission_Register&diff=547&oldid=prev 2013-04-05T05:09:49Z

<p>GF added</p> <p><b>New page</b></p><div>{{Maturity|2}}<br /> {{Pageheaderbox4GF<br /> |name=Permission Register<br /> |WorkingArea=Middleware<br /> |version=0.3<br /> |owner=J.A.H. Schoonderbeek<br /> |summary=This function offers a means to store and publish permissions (technical representations of business rules about infrastructural actions like reading or writing information).<br /> }}<br /> This function offers a means to store and publish permissions (technical representations of business rules about infrastructural actions like reading or writing information). It usually accompanies a {{FriendlyPageLink|GF.Permission Validation}} function.&lt;br&gt;<br /> Note that for many systems, its permissions are written in a format specific to that system: the capabilities of a Permission Register with respect to the kinds of permissions it can handle are hard-coded. This means that if a Permission Register (and Permission Validation) facility is positioned in an infrastructure landscape to authorize access to a set of resources, it cannot automatically be assumed fit to also authorize access to a new, different set of resources. E.g. a Permission Register that can hold s access control lists for web URIs cannot be assumed to also be able to hold access rules for a mail application. <br /> <br /> Permission Register is modelled separately from Permission Validation for two major reasons:<br /> * to account for the security aspects (both in the sense that a Permission Register itself must be properly secured, and that positioning a Permission Register in an infrastructure overview serves as a focal point for security considerations), and<br /> * because the permissions that can be stored in a particular Permission Register instance are inherently limited to a specific set of actions for a specific (type of) infrastructure resource (as described above).<br /> {{FunctionIcon<br /> |image=Icon GF Permission Register.png<br /> }}<br /> {{Text Footer GF}}</div>

Jan Schoonderbeek