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 information

Solution information: AS role

It is recommended that the AS provide RO and RqP login credentials that can be used in a programmatic fashion, e.g. in a simple HTML form. It is assumed that the C is client-unaware and will be using the redirect claim profile to redirect the RqP to the AS for login as the sole claims-gathering process.

Solution information: RS role

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. It is RECOMMENDED that each RS document exactly the one or two endpoints/calls/parameters that are sufficient for UMA interop testing purposes, to limit the universe of potential actions that a client can take.

Solution information: C role

As noted above, it is assumed that the C is client-unaware and will be using the redirect claim profile to redirect the RqP to the AS for login as the sole claims-gathering process.