: A new JSON-based parameter used in authorization and token requests.
: Reflect the authorized details in the resulting Access Token or via the Introspection Response for Resource Servers to verify. 3. Security Considerations
This feature enables clients to specify fine-grained authorization requirements, such as requesting access to specific bank accounts or certain transaction amounts, rather than using broad, pre-defined scopes. 1. Core Components 4839005059204218ae8e0c51956c63d6.rar
: Custom fields specific to the type , such as amount , currency , or account_id . 2. Implementation Workflow
: Create a registry of authorization detail types your system supports. : A new JSON-based parameter used in authorization
: Use encrypted or signed tokens (JWTs) if the authorization details contain sensitive transaction data.
The string 4839005059204218ae8e0c51956c63d6.rar appears to be a filename referencing a specification within the OAuth framework. The "proper feature" you are likely looking to draft relates to draft-ietf-oauth-rar , which allows for fine-grained, parameterizable authorization requests beyond simple scopes. Feature Specification: Rich Authorization Requests (RAR) which allows for fine-grained
: A string identifying the type of authorization (e.g., payment_initiation , account_information ).
