Changes between Version 13 and Version 14 of UniformClearinghouseAPIV2
- Timestamp:
- 11/12/13 11:54:07 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UniformClearinghouseAPIV2
v13 v14 85 85 * CREDENTIAL_TYPES: A list of recognized credential types (e.g. [geni_abac, geni_abac]) and list of supported credential versions on protected API methods. Format is analogous to that in the AM API: a list of {"type": cred_type, "version" : cred_version} dictionaries of all supported credential types and versions. ''[Authorities only]'' 86 86 * ROLES : A list of recognized roles for slice/project membership (optional for those Slice Authorities supporting membership). ''[SA only]'' 87 * FIELDS: A dictionary of '''''supplementary'''''object field names (i.e. in additional to the required fields) and associated attributes including:87 * FIELDS: A dictionary of object field names (i.e. in additional to the required fields) and associated attributes including: 88 88 * “OBJECT” provides the object to which the field belongs (if not the default authority object, i.e. SLICE for Slice Authority, MEMBER for Member Authority, SERVICE for Registry). This field is mandatory for any field listed. 89 89 * “TYPE” may be one of “URN”, “UID”, “STRING”, “DATETIME”, “EMAIL”, “KEY”,“BOOLEAN”, “CREDENTIAL”, “CERTIFICATE”. [NB. This set of types subject to change. See Appendix for more information on these data types.] This field is mandatory for any field listed. … … 93 93 * “PROTECT” attributes may be labeled as “PUBLIC”, “PRIVATE” or “IDENTIFYING”. These are for the Member Authority Only to differentiate between public, identifying and private data fields on members. The default, if not provided, is "PUBLIC", and thus this attribute is optional. 94 94 95 The FIELDS element of the get_version is optional for all services, as it only contains supplementary fields (which may not exist for a given service).95 The FIELDS element of the get_version should contain all supplementary (non-mandatory) field objects supported by a given service. Additionally, it should contain mandatory field objects for which the default semantics (for "CREATE", "MATCH", "UPDATE", "PROTECT") should be overridden. The FIELDS element is thus optional for all services. 96 96 97 97 Supplementary field names should be placed in a distinct namespace by a prefix unique to that federation, and starting with an underscore (e.g _GENI_, _OFELIA_ , _FED4FIRE_ or _PROTOGENI_ etc.). … … 1003 1003 || || update_key || update(type="KEY") || 1004 1004 || || lookup_keys || lookup(type="KEY") || 1005