Changes between Version 4 and Version 5 of UniformClearinghouseAPI


Ignore:
Timestamp:
08/14/13 15:12:06 (6 years ago)
Author:
jmccolga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UniformClearinghouseAPI

    v4 v5  
    116116
    117117}
     118
     119The following is an example of a return from a get_version for an MA, provided in JSON-like syntax:
     120
     121{
     122
     123      “VERSION”: “10.0.7”,
     124
     125      “CREDENTIAL_TYPES”: [“SFA”, “ABAC”],
     126
     127      “FIELDS”: {
     128   
     129              “MEMBER_DISPLAYNAME”: {“TYPE”: “STRING”, “CREATE”: “ALLOWED”, “UPDATE”,
     130
     131TRUE, “PROTECT”: “IDENTIFYING”},
     132
     133      “MEMBER_AFFILIATION”: {“TYPE”: “STRING”, “CREATE”: “ALLOWED”, “UPDATE”:
     134
     135TRUE, “PROTECT”: “IDENTIFTYING”},
     136
     137      “MEMBER_SPEAKS_FOR_CREDENTIAL”: {“TYPE”: “CREDENTIAL”},
     138     
     139      “MEMBER_SSL_PUBLIC_KEY”: {“TYPE”: “SSL_KEY”},
     140
     141      “MEMBER_SSL_PRIVATE_KEY”: {“TYPE”: “SSL_KEY”, “PROTECT”: “PRIVATE”},
     142
     143      “MEMBER_SSH_PUBLIC_KEY”: {“TYPE”: “SSH_KEY”},
     144
     145      “MEMBER_SSH_PRIVATE_KEY”: {“TYPE”: “SSH_KEY”, “PROTECT”: “PRIVATE”},
     146
     147      “MEMBER_ENABLED”: {“TYPE”: “BOOLEAN”, “UPDATE”: TRUE}