Authorization details — Versola Docs
/docs
Pre-1.00.7.5versola.ioGitHub
RUEN

Authorization details

Reference for the Authorization details page of the admin console — registering the RFC 9396 authorization_details types that clients of a tenant may request

The Authorization details page registers the RFC 9396 authorization_details types that clients of a tenant may request. Pick the tenant in the sidebar first; the types belong to it. A detail object of a registered type is rejected unless it validates against the type’s schema.

Before you start

NeedPermission
See the pagesecurity:read
Create, edit or delete a typesecurity:manage

Without security:manage the page is read-only: + Create Type, the Edit buttons and the delete actions are not shown.

The list

Authorization details, the list
Authorization details page: a search field and a table of registered types with the description and type ID, a schema summary and the languages that have a description.

Each row shows the type’s description with its ID, a summary of its schema and, when the deployment has active languages, which of them have a description. The search field matches the type or the description. The row menu offers Open, Copy type and Delete type. Selecting a row opens its side panel.

The type panel

A type in its side panel
The side panel of the payment_initiation type: the General card with the description, the JSON Schema card with the schema in a code editor view, and the Fixed card with the type.

The panel holds three cards and a delete action:

  • General: the Description, with Edit.
  • JSON Schema: the schema that detail objects of this type are validated against, with Edit.
  • Fixed: the Type, set at creation. Clients send it as the type member; to change it, delete the type and create a new one.
  • Delete type, after a confirmation: clients can no longer request the type in authorization_details.

Create a type

+ Create Type opens the panel in create mode.

Create type
The Create type panel with the Type field, a localized Description field and a JSON Schema code editor prefilled with a 2020-12 starter schema.
FieldRules
TypeThe value clients send as the type member. Lowercase letter first, then lowercase letters, digits and underscores (payment_initiation).
DescriptionRequired, one text per active language; English is required, the others are optional. The consent screen shows it.
JSON SchemaRequired. JSON Schema 2020-12, written in a code editor. Detail objects of this type are rejected unless they validate against it; unevaluatedProperties: false rejects unknown members. Central refuses a schema that is not itself a valid JSON Schema, and the console shows its message under the editor.

The form is prefilled with a starter schema that requires type and allows locations and actions as string arrays. Central adds each type to authorization_details_types_supported in the server metadata and removes it again on delete.

Next steps