Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page gathers information about implementation efforts and interest, along with interoperability testing plans. We have a goal to develop a hosted validator that can exercise implementors' AM, Host, Requester, and User Agent endpoints to increase interoperability. To this end, we undertook a bounty program in 2010 that facilitated the creation of test cases. Interop testing activities are now centered on the OSIS wiki, in the "UMA1" namespace area. We are currently filling in the interop participants, their solutions (potentially more than one for each participant), testable features of the UMA specs, and specific feature tests, with the wiki to be populated with interop testing results by the actual participants.

Maciej Machulak is the UMA group's implementation coordinator. Several efforts are gearing up in earnest now.

Interest and effort mentioned so far (no obligation implied!):

Who

Protocol: AM

Protocol: Host

Protocol: Requester

UX: "relationship manager"

Notes

Newcastle University SMART project (including the SMART AM, sample host and requester, and the underlying UMA/j library)

(tick)

(tick)

(tick)

(tick)

SMART project developed in Java, including UMA/j framework, sample applications, and OAuth implementation. See the SMART blog. The OAuth portion, originally named leeloo, has been contributed to Apache Amber. The rest is anticipated to be open-sourced soon.

Fraunhofer AISEC

(tick)

(tick)

(tick)

(tick)

Working on a mobile location scenario. Based on Submitted as open source to Apache Amber. To be demonstrated in fall 2011Demonstrated in April 2012. See draft V0.6 7 of implementation doc. Update from the team as of 9 Jul 2012: "UMA client, AM, and Host are running now within AISEC domain and will be accessible from the outside after receiving the security clearance from our network team".

MITRE/Project hData

(question)

(question)

(question)

(question)

Considering implementation of a health data-specific profile that matches Project hData needs and an implementation of an UMA-compliant native-app requester.

Christian Scholz/COMlounge.net

(tick)

(tick)

(tick)

(tick)

Prototype and demo in Python. Now out of date compared to the latest specs.

Azigo

(tick)

(tick)

 

(tick)

Intends to do an UMA-compliant implementation.

Connect.me

(tick)

(tick)

 

(tick)

Intends to do an UMA-compliant implementation.

Mydex

(tick)

(tick)

 

(tick)

Intends to do an UMA-compliant implementation.

Neustar

(question)

(question)

 

 

Interested in doing a mobile-based AM prototype.

The Customer's Voice

(tick)

(tick)

(tick)

 

Planning to implement UMA, likely to begin Feb/ March 2012 with a VRM oriented application.

Open Source Currency    Tom Brown of Open Source Currency has implemented the dynamic client registration spec that was contributed to IETF for consideration and accepted as a work item by the OAuth WG. It is running as a demo.