Changes between Version 10 and Version 11 of GeniAuthorization

Timestamp:

10/31/12 13:44:31 (11 years ago)

Author:

Aaron Helsinger

Comment:

--

GeniAuthorization

@@ -4 +4 @@
 GENI requires an authorization solution that will allow architectural components (Clearinghouse, Aggregates) to determine the privileges of an experimenter. Experimenters can be granted privileges based on institutional affiliation, project role or membership attributes, for instance. Aggregates are expected to have local policies regarding resource access and use. 
 
+For current authorization credentials used in the GENI AM API, see GeniApiCredentials. Longer term, [http://abac.deterlab.net/ ABAC credentials] are expected to be the mechanism used for authorization. See also discussions in the [wiki:GeniArchitectTeam GENI Software Architecture].
+
+'''This page needs improvements, to provide a better summary.'''
+
 = GEC 13 Engineering Meeting =
 == Summary ==
 GEC 13 marked the completion of the ABAC evaluation period in the software track of the GECs over the last year. There were a number
 of invited talks by individuals or projects that have spent time evaluating ABAC and prototyping ABAC integration. After the invited talks
-there was open discussion and a sense of the room was taken. ABAC was adopted as the long-term authorization framework for GENI.
+there was open discussion and a sense of the room was taken. '''ABAC was adopted as the long-term authorization framework for GENI.'''
 
 == Introduction ==