User-centric API Access control using UMA
summary
UMA (User Managed Access) is a specification (in development since 2009) that solves authorization only, not identity or authentication, and aligns with EU data protection principles. It implements OAuth-like roles so a user uploads a resource to a resource server and registers the resource with an authorization server, a requesting client triggers the server to declare required permissions, the user grants access and the client presents a token which the resource server verifies via authorization server introspection. Separation of AS and RS lets users pick distinct services to control sharing.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:15What is UMA?
- 3:05What is UMA about?
- 5:15How does it work?
- 6:44First: Register Resource
- 7:41Second: Authorize Access
- 8:57Third: Access Resource
- 9:29UMA for Resource Server
related talks
39mUnified permission management between API and client
44mUAA Project Updates and Roadmap - Sree Tummidi, Pivotal
31mUser Account and Authorization Server at SAP
43mOAuth is DAC. What do you do for MAC?
23mOne Login to Rule Them All: Cross-App Access for MCP
41mUAA Feature Updates and 2017 Roadmap
31mCloud Foundry UAA as an Identity Proxy Product Roadmap
19mUSEC: A User-Requirement-Driven Mandatory Access Control Framework for Operating Systems