UMA1 Interop Participants and Solutions
...
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 supply:
...
fill out their relevant rows in the following table, including:
- Any particular desired testing partners or partner types
- Which optional and profile-specific feature tests the participant is wishing/willing to test with partners
- AS role only:
TBS (how How RS and C participants can get client credentials if not dynamic, ?) - Link to the AS configuration data dynamically
- RS role only:
- TBS (API documentation, ?)
TBSThe API exposed and any SDK available for clients to use in integrating with the RS
Participant name and logo | Contact names/emails | Solution full name | Solution abbrev | Role (AS, RS, C) | Configuration data (AS only) | Other details |
---|---|---|---|---|---|---|
Gluu (logo, handle) | OXAuth | OX | AS | Link? | ||
RS | ||||||
C? | ||||||
Apache plugin? | AP | RS? | ||||
Cloud Identity Limited, (logo, handle) | SMART | SM | AS | Link? | ||
RS | ||||||
C | ||||||
PUMA | PU | RS | ||||
C | ||||||
Criterion Systems | CR | AS? | Link? | |||
RS? | ||||||
C? | ||||||
Roland Hedberg | RH | AS? | Link? | |||
RS? | ||||||
C? | ||||||
Intel | IN | AS? | Link? | |||
RS? | ||||||
C? | ||||||
ForgeRock | FR | AS | Link? | |||
RS? | ||||||
C? | ||||||
...
Record rollup results in this matrix. An example cell for a FOO:BAR comparison might read: Detected failures when FOO is AS and BAR is RS or C. When FOO is RS and BAR is AS, succeeds.
→Solution 2→ | OX | SM | PU | ... | ... |
---|---|---|---|---|---|
OX | - | ||||
SM | - | ||||
PU | - | ||||
... | - | ||||
... | - |
...