Page Comparison

...

• Breaking changes:
  • (Technically breaking but not expected to have huge impact:) TLS/HTTPS is now mandatory for the AS to implement in its protection and authorization APIs.
• Other changes of note:
  • It is no longer required for the client to redirect a human requesting party to the AS for the claims-gathering process.
  • A new claims profiling framework (now in a separate spec) describes how to leverage one of several common patterns for claims-gathering: client redirects the requesting party to AS, client pushes claims to the AS.
  • A new framework for API extensibility, and a matching series of extensibility profiles, appears in the core spec. It enables tighter coupling between the AS and RS, AS and client, and RS and client, respectively, but only in a controlled manner to foster greater interoperability in such circumstances.
  • The SHOULD for the usage of the SAML bearer token profile for PAT issuance is now just a MAY.
  • In Section 4.2, the example was corrected to remove a wayward "status" : "error" property.
  • Clarified that no request message body is expected when the client uses the RPT endpoint at the AS.
  • Added a success example in Section 3.4.2 showing how authorization data is added and the RPT is simultaneously refreshed, a new capability.

From Core rev 10 to rev 11a-11e (not yet submitted to IETF; mistakenly published as revs 11, 12, 13 on the KI site!):

• Breaking changes:
  • Section 3.4: not_authorized_permission error code: Changed to not_authorized.
  • RPT handling: Changed extensively to remove the RPT issuance endpoint and enable the authorization data request endpoint to do all RPT issuance duties. Permission ticket issuance is now handled on an "eager" basis, when a client either without an RPT or with an invalid or insufficient-authorization-data RPT approaches the RS seeking access. This affects several sections:
    • Section 1.4: configuration data
    • Section 3: introduction
    • Section 3.1.1 and 3.1.2: client approaching RS
    • Section 3.2: RS registering permission
    • Section 3.4: RPT issuance and authorization data addition
    • Section 5.2: Extensibility profile implications
  • Section 1.4 ("12" to "13"):
    • Changed the claim_profiles_supported property in the configuration data to claim_token_profiles_supported
    • Changed the user_endpoint property in the configuration data to authorization_endpoint, to match the final IETF RFC 6749 name in OAuth 2.0
    • Changed the authorization_request_endpoint property in the configuration data to rpt_endpoint, to distinguish it more fully from the OAuth endpoint and to shorten it
    • (Also affects Section 5) Changed how uma_profiles_supported works, so that the API extensibility profiles don't have reserved keywords but rather use the regular URI mechanism for indicating profiles
  • Section 3.3.2:
    • Names of several properties in the permissions structure for the RPT "Bearer" token introspection response have changed to align them with JWT names: expires_at to exp, issued_by to iat.
    • The JWT "scope" property at the top level is now disallowed in favor of "scopes" at the permissions level.
  • PAT and AAT OAuth scopes:
    • These are renamed Renamed from URIs to simple strings: "uma_protection" and "uma_authorization". The ; the JSON scope description documents provided to enable the old URIs to resolve no longer have any relation to the UMA Core spec.
• Other changes of note:
  • Section 3.1.1 and Section 3.1.2: Extraneous host_id removed from example of RS's response to client.
  • ("11" to "12") Enabled explicit use of OAuth-based authentication protocols such as OpenID Connect for OAuth protection driving PAT and AAT issuance.
  • ("12" to "13") Identifiers Identifiers for spec-defined profiles now use https instead of http
  • ("12" to "13") Migrated Migrated the claim profiling spec's requesting party claims endpoint configuration data to the core spec, and made it optional to supply.
  • ("12" to "13") Migrated Migrated the claim profiling spec's "need_claims" extensions to the core spec, broadened it to "need_info", and gave it "error_details" hints in the core spec.
  • Section 3.1.1: Requirement for RS to return 403 to a tokenless client has been softened to a SHOULD.
  • Section 3.3.2: The token introspection response has been aligned with the latest token introspection spec. nbf has been added at the permissions level, exp is now optional, and all permissions-level properties that duplicate JWT-level claims in intent now get overridden by any JWT-level claims present in the response. Finally, the "permissions" JWT claim has been registered with IANA.
  • Extensive new redirect-pattern claims gathering support added
  • Extensive new security and privacy considerations added

...

• Breaking changes:
  • Section
  3
  • 1.4
  .1.2Section 1.4:
  • :
    • redirect_user: Changed from string values of "yes" and "no" to Boolean values of true and false.
    Changes of note:
    • • issuer property: Now required to match the actual published location of the config data.
      • Dynamic client configuration: When OIDC dynamic client configuration is used, this is now more intelligently handled through a reserved keyword "openid" that indicates that the OIDC configuration data should be consulted for the relevant endpoint.
      • pat_grant_types_supported and aat_grant_types_supported: Broadened to allow them to be strings even when not based on the OAuth grant type strings, similarly to token profiles.
      • issuer property: Now required to match the actual published location of the config data.
      • Dynamic client configuration: When OIDC dynamic client configuration is used, this is now more intelligently handled through a reserved keyword "openid" that indicates that the OIDC configuration data should be consulted for the relevant endpoint.
      • pat_grant_types_supported and aat_grant_types_supported: Broadened to allow them to be strings even when not based on the OAuth grant type strings, similarly to token profiles.

  From RSR rev 03 to rev 04:

  • Breaking changes:
    • Removed the "status: xxx" property from all the AS responses in the RSR API.
  • Other changes of note:
    • ("04" to "05") Added a new optional resource_uri parameter to the resource set description, to support resource discovery at an authorization server.
    • Scopes bound to resource set descriptions can now be strings rather than being required to be URIs that resolve to scope description documents.
    • The _rev property has been removed from the resource set registration API. It can be added back as an extension for those who want it.

  ...