UMA1 Interop Participants and Solutions
Go to Features and Feature Tests page
Go to main UMA1 Interop Testing page
Visit the uma-dev list archive
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:
- Links to participant's organization, organization logo, and Twitter handle (if any)
- Names and emails of 1-2 key contacts participating in the interop and available during the interop event
- Whether the contacts will be participating F2F or virtually
- Which UMA roles are covered in each solution
- Any other relevant details as discussed below:
- TBS (any particular desired testing partners, how many wired network drops needed if participating F2F, static IP addresses required, any special requests for the event or venue, ?)
- Which optional and profile-specific feature tests the participant is willing to test with partners
- AS role only:
- TBS (how RS and C can get client credentials if not dynamic, ?)
- Link to the AS configuration data
- RS role only:
- TBS (API documentation, ?)
- C role only:
- TBS
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? | ||||||
Results
Record feature-test-specific results in this matrix. An example result for a FOO:AS-to-BAR:RS interaction attempt regarding the F-as-config test might read: FT-rs-get-config-data failed. Config data from FOO:AS was malformed.
Solution:role 1
| Solution:role 2 | Test ID(s) | Result |
---|---|---|---|
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 | - | ||||
... | - | ||||
... | - |