Changes between Version 37 and Version 38 of GAPI_AM_API_DRAFT

Timestamp:

03/06/12 10:20:07 (13 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_DRAFT

@@ -664 +664 @@
 
 = Change Set L: Change SFA credentials' privileges =
-Our goal is to simplify and standardize privilege strings. Currently there are wildcards, bind, embed, and others. They are confusing. We also want extensibility to use these credentials elsewhere in future. 
+Our goal is to simplify and standardize privilege strings used in SFA credentials. Currently there are wildcards, bind, embed, and others. They are confusing. We also want extensibility to use these credentials elsewhere in future. 
 
 Credentials should support these kinds of operations:
@@ -688 +688 @@
 
 Privilege and credential semantics are defined as follows: 
- - Aggregates may only grant access to a method if at least one valid credential 
-  - grants the required privilege (if any) 
+ - Aggregates may only grant access using current SFA credentials to a method if at least one such valid credential: 
+  - grants the required privilege or privileges (if any) 
   - to the caller of the API method 
    - (identified by their SSL client certificate and the {{{owner_gid}}} in the credential) 
   - over the slice (if any) on which they are operating 
    - ({{{target_gid}}} in the credential). 
- - Other privileges may be present in the same or other credentials. 
+ - Other privileges may be present in the same or other credentials, and other non-SFA credentials may be used to authorize actions (per [#ChangeSetG:Credentialsaregeneralauthorizationtokens. Change Set G].
  - Local aggregate policy may deny access to a particular method even in the presence of a valid credential granting the required privilege.
  - Some operations (e.g. !GetVersion) may either simply require a valid credential with no particular privilege, or have no {{{credentials}}} argument at all.
 
-Note also that some current AMs do not require any particular privileges to do !ListResources, even with a {{{slice_urn}}}. This change explicitly requires that aggregates require a valid slice credential with {{{CanRead}}} privileges to perform this operation.
+Note also that some current AMs do not require any particular privileges to do !ListResources, even with a {{{slice_urn}}}. This change explicitly requires that aggregates require a valid slice credential with {{{CanRead}}} privileges to authorize this operation using current slice credentials.
 
 -----