| Info |
|---|
Welcome to the UMA Dev Resources WG group. We're just getting started. Now is a great time to JOIN the community! |
| Panel |
|---|
| borderColor | #99cc00 |
|---|
| bgColor | #ffffff |
|---|
| borderWidth | 4pt |
|---|
| title | Have YOU joined yet? |
|---|
|  Image Added Thanks to vice-chair Maciej Machulak for the image above – it's a good reminder that "UMAnizing" websites and web apps can help add security and privacy features. The UMA V1.0 specifications have been approved as Kantara Initiative Recommendations – UMA Core V1.0 specification (Kantara Recommendation, IETF I-D rev 13) and OAuth Resource Set Registration V1.0 specification (Kantara Recommendation, IETF I-D rev 06). Check out our User Experience page to explore different user experience paradigms. |
JOIN | SUBSCRIBE | MAILMAN ARCHIVE 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 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. |