Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

F-as-config: AS makes available its configuration data in the correct form at the correct location

The feature tests in this section have been reviewed.

This feature is about machine-readability of capabilities and constraints.

...

F-dyn-client-reg: AS supports generating dynamic client credentials and RS and client support getting them

The feature tests in this section have been reviewed.

This feature is about client registration of resource servers (which are clients of the AS's protection API) and clients of resource servers (which are also clients of the AS's authorization API) at run time when services have not "met" before a resource owner or requesting party forces the issue.

...

F-pat: AS successfully issues PAT to RS for use at AS's protection API

The feature tests in this section have been reviewed.

This feature is about "protection of the protection API" at the authorization server, and the association made between the authorization server, resource server, and resource owner as a result of protection API token (PAT) issuance.

...

F-aat: AS successfully issues AAT to Client for use at AS's authorization API

The feature tests in this section have been reviewed.

This feature is about "protection of the authorization API" at the authorization server, and the association made between the authorization server, client, and requesting party as a result of authorization API token (AAT) issuance.

...

F-rsr: RS registers resource sets at AS in order to put them under AS protection

The feature tests in this section have been reviewed.

This feature is about putting resources under protection by a third party.

...

F-protect-rsrc: RS, AS, and client interact to enable authorized access to protected resources and block unauthorized access

The feature tests in this section have not yet been reviewed.

This feature is about protecting resources in practice, at run time. This involves a successive series of "gates": having a valid RPT, supplying any claims needed to assess against policy, having valid authorization data that matches the type of access sought, etc.

...