You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 32
Next »
UMA1 Interop Participants and Solutions
Main UMA1 Interop Testing page | Features and Feature Tests | Results | uma-dev list
Participants in UMA1 testing must register on this page, either by editing the page or by contacting the UMA WG chair, and should subscribe to the uma-dev mailing list, which will be used for interop-related communications. No ranking of other special meaning should be attached to the order in which participants appear. Participants must fill out their relevant rows in the following tables:
Participant name and logo | Contact names/emails | Solution full name | Solution abbrev | Roles (AS, RS, C) |
---|
Gluu (logo, handle) |
| OXAuth | OX | AS, RS, C? |
Apache plugin? | AP | RS? |
Cloud Identity Limited, (logo, handle) | Maciej Machulak (maciej.machulak(AT)cloudidentity.co.uk) | NuveAM | CI | AS, RS, C |
| | Python/Java UMA | PU | RS, C |
Roland Hedberg | roland.hedberg-at-adm.umu.se | PyUMA | RH | AS, RS, C |
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.