...
Solution information: RS role
Any API exposed by an RS participating in the interop MUST be "pbryan" API-compatible to provide predictability to clients participating in the interop. If a participant claims hardship and is also prepared to expose a well-known, well-defined API such as SCIM or FHIR, and at least one other party participating in the interop also has an interest in that specific API, we can consider creating a results list subset for the testing among that sub-community.
| Solution:role | API info | SDK avail? | Login URL and RO creds | Protected resource URL(s) info | Expects dynamic client registration at AS? | Other details |
|---|---|---|---|---|---|---|
| OX:RS | ||||||
| CI:RS | https://nuvepds.appspot.com/about/api | Python and Java | https://nuvepds.appspot.com (Sign in with your social profile) | https://nuvepds.appspot.com/about/api | Optional | |
| RH:RS | Uses "pbryan" (http-json-resource) | https://xenosmilus.umdc.umu.se:8777/login.html (user:alice, password:krall) | Base URL for alice's resources: https://xenosmilus.umdc.umu.se:8777/json/alice | Supports webfinger. Supports acct and http identifier urls. |
...