Changes between Version 4 and Version 5 of AaronHelsinger/GAPI_AM_API_DRAFT2


Ignore:
Timestamp:
04/04/12 11:03:21 (7 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AaronHelsinger/GAPI_AM_API_DRAFT2

    v4 v5  
    5454 - '''ADOPTED''' with changes: Change Set I2: !SliversStatus return includes SSH logins/key for nodes that support SSH access
    5555 - '''ADOPTED''': Change Set I3: !CreateSlivers return becomes a struct, adds sliver expiration
    56  - '''ADOPTED''': wiki:AaronHelsinger/GAPI_AM_API_DRAFT2#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K]: Standardize certificate contents, etc
     56 - '''ADOPTED''': [wiki:AaronHelsinger/GAPI_AM_API_DRAFT2#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K]: Standardize certificate contents, etc
    5757  - Include a real serial number, holder email, holder uuid, and optionally authority URL in certificates
    5858  - Define slice ID as the UUID plus URN in slice certificates
     
    313313
    314314 - An AM must pick credentials out of the list that it understands and be robust to receiving credentials it does not understand.
    315   - Current slice and user credentials will be recognizable for following the schema defined in [#ChangeSetK:Standardizecertificatesandcredentials Change Set K].
     315  - Current slice and user credentials will be recognizable for following the schema defined in [#Adopted:ChangeSetK:Standardizecertificatesandcredentials Change Set K].
    316316 - AMs are required to continue to accept current-format credentials.
    317317  - In particular, a single standard slice credential remains sufficient for most authorization policies.