Versions Compared

Key

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

UMA Interoperability Testing

We are preparing UMA interoperability and conformance feature tests for the first UMA interop to be held October 31 and November 1, 2013 at MIT in Cambridge, MA, USA. If you would like to be a participant in this process, please register. Attached is a draft set of features and feature tests for review; these will eventually appear on the OSIS interop wiki. Participants so far include:

  • Gluu
  • Cloud Identity UK
  • Criterion Systems
  • Roland Hedberg (test harness)
  • Intel
  • ForgeRock

Following are notes about the construction of features and tests.

  • The feature_id always starts with F-.
  • The feature test identifier always starts with FT-.
  • For features, the feature_type value can be either interop or optional.
  • For feature tests, the testtype value can be either normal or optional.
  • The testedrole can be AM, H, or R.
  • The features and tests relate exclusively to the core protocol spec and to software components that serve as protocol endpoints. None relate to the Binding Obligations document because this document describes expected behaviors of operators and users of these endpoints, which makes them untestable for the purposes of an interop.

 

 Participants and Solutions | Features and Feature Tests | Results

The two UMA specifications – UMA Core and OAuth Resource Set Registration – have reached V1.0 Candidate status in preparation for consideration as Kantara Initiative Recommendations in early 2015. Interop testing has begun.

You can use the short link "http://tinyurl.com/uma1iop" to return to this page.