You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 33
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 RS participating in interop has to expose either multiple resource sets (as registered with the AS) or multiple scopes, or both. This enables testing UMA-specific interop around sufficient/insufficient authz data, permission tickets that match/don't match the requested type of access, etc., while not dictating the specifics of what the API looks like. Each RS participant needs to provide enough information directly in the table below to explain how to access these differential resource sets and scopes, e.g. the URLs, parameters, etc. This way, clients can tell whether the RS was at fault or not if something goes wrong with authorization.
