Changes between Version 3 and Version 4 of GAPI_AM_API


Ignore:
Timestamp:
08/04/10 10:47:15 (9 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GAPI_AM_API

    v3 v4  
    5151
    5252 `credentials[]`::
    53     An array of credentials. At least one credential must be valid for this operation (signed by a valid GENI certificate authority either directly or by chain, and not expired).
     53    An array of credentials. At least one credential must be valid for this operation (signed by a valid GENI certificate authority either directly or by chain, and not expired). Note that the semantics of this argument is not clear. Alternative interpretations might, for example, accumulate privileges from each valid credential to determine overall caller permissions.
    5454
    5555 `options`::
     
    9797
    9898 `credentials`::
    99    An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}.
     99   An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}. Note that the semantics of this argument is not clear. Alternative interpretations might, for example, accumulate privileges from each valid credential to determine overall caller permissions.
    100100
    101101 `rspec`::
     
    123123
    124124 `credentials`::
    125    An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}.
     125   An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}. Note that the semantics of this argument is not clear. Alternative interpretations might, for example, accumulate privileges from each valid credential to determine overall caller permissions.
    126126
    127127Returns true on success and false on failure.
     
    143143
    144144 `credentials`::
    145    An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}.
     145   An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}. Note that the semantics of this argument is not clear. Alternative interpretations might, for example, accumulate privileges from each valid credential to determine overall caller permissions.
    146146
    147147Returns an XMLRPC struct upon successful completion. The struct is of the following form:
     
    202202
    203203 `credentials`::
    204    An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}.
     204   An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}}. Note that the semantics of this argument is not clear. Alternative interpretations might, for example, accumulate privileges from each valid credential to determine overall caller permissions.
    205205
    206206 `expiration_time`::
    207     A string in [http://tools.ietf.org/html/rfc3339 RFC 3339] format indicating the expiration_time desired by the caller. This time must be less than or equal to the slice duration in the slice credential.
     207    A string in [http://tools.ietf.org/html/rfc3339 RFC 3339] format indicating the expiration_time desired by the caller. This time must be less than or equal to the slice duration in the slice credential. In other words, at least one supplied (slice) credential must still be valid at the desired new expiration time for this call to succeed.
    208208
    209209
     
    226226
    227227 `credentials`::
    228    An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}} or a valid administrative credential with sufficient privileges.
     228   An array of credentials. At least one credential must be a valid slice credential for the slice specified in {{{slice_urn}}} or a valid administrative credential with sufficient privileges. Note that the semantics of this argument is not clear. Alternative interpretations might, for example, accumulate privileges from each valid credential to determine overall caller permissions.
    229229
    230230Returns true on success, false otherwise.