UMA Release Notes
Abstract
This document contains non-normative release notes produced by the User-Managed Access Work Group explaining how new versions of the UMA specifications differ from previous ones.
Status
This document includes release notes for all versions of UMA.
Editor
Eve Maler
Intellectual Property Notice
The User-Managed Access Work Group operates under Kantara IPR Policy - Option Patent & Copyright: Reciprocal Royalty Free with Opt-Out to Reasonable And Non discriminatory (RAND) (HTML version) and the publication of this document is governed by the policies outlined in this option.
The content of this document is copyright of Kantara Initiative. © 2018 Kantara Initiative
Table of Contents
- 1 Abstract
- 2 Introduction
- 3 From UMA1 to UMA V2.0
- 3.1 Version Themes
- 3.2 Specification Reorganization and Conformance Levels
- 3.3 Terminology Changes
- 3.4 API and Endpoint Changes
- 3.5 Authorization Server Discovery Document and Metadata Changes
- 3.6 Changes to AS-Client, RS-Client, and AS-Requesting Party Interfaces (Now UMA Grant Specification)
- 3.6.1 Authorization Server Rotates Permission Ticket
- 3.6.2 Token Endpoint Replaces RPT Endpoint; Client-Side Communications Defined as Extension Grant
- 3.6.3 AAT Removed in Favor of PCT
- 3.6.4 Deprecated Response-Body Permission Ticket Return Option By RS Removed
- 3.6.5 Permission Ticket Return By AS With Redirect-User Hint No Longer Deprecated
- 3.6.6 More Discretionary Permission Requests
- 3.6.7 need_info Response Structured Flattened
- 3.6.8 not_authorized Error Renamed to request_denied
- 3.6.9 New Refresh Token Clarity
- 3.6.10 Authorization Assessment Gains Precision
- 3.6.11 Permission Ticket Ecosystem Rationalized
- 3.6.12 Only One Pushed Claim Token Now Allowed at a Time
- 3.6.13 RPT Upgrading Logic Improved
- 3.6.14 Token Revocation Clarifications
- 3.6.15 Refresh Token Grant and Downscoping Logic Clarifications
- 3.7 Changes to AS-RS Interface/Protection API (Now Federated Authorization Specification)
- 3.7.1 Resource Registration Endpoint
- 3.7.1.1 Extraneous URL Parts Removed From Resource Registration API
- 3.7.1.2 Scope Description Documents No Longer Expected to Resolve at Run Time When Scopes Are URLs
- 3.7.1.3 Resource Descriptions Lose uri Parameter
- 3.7.1.4 Resource and Scope Description Documents Gain Description Parameters
- 3.7.1.5 scopes Parameter in Resource Description Document Renamed to resource_scopes
- 3.7.1.6 New HTTP 400 and invalid_request Error
- 3.7.2 Permission Endpoint
- 3.7.3 Token Introspection Endpoint
- 3.7.1 Resource Registration Endpoint
- 4 From V1.0 to V1.0.1
- 4.1 Changes Affecting Authorization Server (+Client) Implementations
- 4.1.1 AS Now Has Unique Redirect URI Endpoint for Claims Gathering (+Client)
- 4.1.2 Permission Ticket Lifecycle Management (+Client)
- 4.1.3 Requested Permission and Permission Ticket Matching
- 4.1.4 Permission Ticket on Redirect Back to Client (+Client)
- 4.1.5 PUT Means Complete Replacement
- 4.1.6 Default-Deny for Authorization Data Issuance
- 4.1.7 base64url-Encoded Claims (+Client)
- 4.1.8 Enhanced Security Considerations
- 4.1.9 Enhanced Privacy Considerations
- 4.2 Changes Affecting Resource Server (+Client) Implementations
- 4.3 Specification Reorganizations
- 4.1 Changes Affecting Authorization Server (+Client) Implementations
- 5 Pre-V1.0 Changes
- 5.1 Core Changes
- 5.2 RSR changes
- 5.3 Claim Profiles changes
- 5.3.1 Claim Profiles Rev 00
- 6 Change History