UMA1 Interop Features and Feature Tests
...
- config: Machine-readability of entity capabilities and constraints.
- dynreg: 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.
- pat: "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.
- aat: "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.
- protapi: RS-AS communication through the protection API and its various endpoints.
- authzapi: C-AS communication through the authorization API and its various endpoints.
- access: C-RS communication through the UMA-protected resource interface for the purpose of attempting and granting or denying access.
- error: Requirements for error messages.
"config" feature tests
Machine-readability of entity capabilities and constraints.
asdf
Feature tests for "config"
asdf
| Identifier | Required? | Description | Success |
|---|---|---|---|
| FT-as-config-data | req | AS provides configuration data that conforms to specified formatformats and provides all required properties | Data conforms to format requirementsand is complete
|
FT-as-config- endptsendpt | req | AS makes config data available through https://\{as_uri}/.well-known/uma-configuration | AS config data endpoint uses https: scheme with specific URL form, with a valid certificate |
| FT-rs-get-config-data | opt | RS successfully accesses and parses AS config data properties it needs at https://\{as_uri}/.well-known/uma-configuration, including all endpoint-related properties not specific to the RS and including handling of non-understood extension properties | RS successfully accesses and parses AS config data |
| FT-c-get-config-data | opt | Client successfully accesses and parses AS config data properties it needs at http://\{as_uri}/.well-known/uma-configuration or https://{as_uri}/.well-known/uma-configuration, including all endpoint-related properties not specific to the client and including handling of non-understood extension properties | Client successfully accesses and parses AS config data |
...