UMA1 Interop Participants and Solutions

Participants are required to register on this page, either by editing the page or by contacting the UMA WG chair, by Monday, October 14, 2013. 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, ?)
- 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	F2F or virtual	Solution full name	Solution abbrev	Role (AS, RS, C)	Configuration data (AS only)
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 is supplied in the first row in fuchsia.

Solution:role 1	Solution:role 2	Feature tested	Result
OX:AS	SM:RS	F-as-config	FT-rs-get-config-data failed. Config data from OX:AS was malformed.

Record rollup results in this matrix. An example result is supplied in the first row in fuchsia.

→Solution 2→ ↓Solution 1↓	OX	SM	PU	...	...
OX	-	Detected failures when OX is AS and SM is RS or C. When OX is RS and SM is AS, succeeds.
OX	-
SM		-
PU			-
...				-
...					-