| Panel |
|---|
| borderColor | #99cc00 |
|---|
| bgColor | #ffffff |
|---|
| borderWidth | 4pt |
|---|
| title | UMA Dev is under way |
|---|
|  We are working on implementing the client side of UMA interactions. Check out our GitHub repo as things progress. |
The purpose of this Work Group is to design and develop free and open-source software (FOSS), in several popular programming languages, that empowers developers to incorporate User-Managed Access (UMA) protection and authorization API enablement into applications, services, and devices, promoting privacy enhancement and broader adoption of UMA ecosystems. The UMA WG’s requirements and design principles encourage simplicity of specific kinds, and on the part of specific system entities, in order to foster ecosystem growth; this group’s purpose supports those aims. Specifically: Design principle 1 states UMA will be Simple: “Simple to understand, implement in an interoperable fashion, and deploy on an Internet-wide scale” Design principle 4 states UMA will be RESTful: “Resource-oriented (for example, as suggested by the REST architectural style) and operating natively on the Web to the extent possible” Design principle 10 describes constraints around Complexity: “Complexity should be borne by the [authorization server] endpoint vs. the [resource server] or [client], if possible”
Read the full charter. Latest news: - We'll be convening a session at IIW in Mountain View in October to discuss interop needs and the state of Roland's codeNov 6:
- At IIW, Roland Hedberg convened a session to review the design progress on his library to implement an initial "attribute release policy" use case.
- The UMA V1.0.1 specifications were approved by the UMA WG as Draft Recommendations.
- Leaders of Industry and Government Converge to Launch the Kantara Initiative UMA Dev WG to Develop Tools for Global Adoption of UMA – read the press release
|