RAR
A draft OAuth 2.0 extension that allows clients to carry structured authorization details (authorization_details) in the authorization request, describing specific operations in JSON and enabling finer-grained authorization expression than scope.
Timeline (last 90 days)
For AI agents connecting to systems, using RAR and DPoP in combination is currently the more pragmatic choice.
Even when combined, the four OAuth extensions still cannot express cross-agent delegation chain traceability in a standardized way.
RAR clearly states the authorization intent, but resource servers lack a general mechanism to compare whether the operation declared in the token matches the operation actually requested.
None of the four extensions provides a unified answer for scenarios such as permission downgrade during refresh of long-running tasks and task interruption recovery.
RAR (Rich Authorization Requests) allows clients to carry a structured authorization_details JSON in the authorization request to describe specific operations.
RAR itself does not verify the identity of the requester, nor does it prevent tokens from being misappropriated.
The internal structure of a RAR file consists of a series of blocks, including header blocks, file blocks, and an end block; each file block records metadata such as the filename, size, compression method, and CRC checksum, as well as the compressed data stream.
Because RAR files are stored contiguously on disk, achieving simultaneous decompression and release requires low-level techniques such as file truncation or sparse files to progressively shrink the archive size
The RAR format (Roshal Archive) was developed by Eugene Roshal in 1993.
All Facts (9)
For AI agents connecting to systems, using RAR and DPoP in combination is currently the more pragmatic choice.
50%UnverifiedEven when combined, the four OAuth extensions still cannot express cross-agent delegation chain traceability in a standardized way.
50%UnverifiedRAR clearly states the authorization intent, but resource servers lack a general mechanism to compare whether the operation declared in the token matches the operation actually requested.
50%UnverifiedNone of the four extensions provides a unified answer for scenarios such as permission downgrade during refresh of long-running tasks and task interruption recovery.
50%UnverifiedRAR (Rich Authorization Requests) allows clients to carry a structured authorization_details JSON in the authorization request to describe specific operations.
50%UnverifiedRAR itself does not verify the identity of the requester, nor does it prevent tokens from being misappropriated.
50%UnverifiedThe internal structure of a RAR file consists of a series of blocks, including header blocks, file blocks, and an end block; each file block records metadata such as the filename, size, compression method, and CRC checksum, as well as the compressed data stream.
50%UnverifiedBecause RAR files are stored contiguously on disk, achieving simultaneous decompression and release requires low-level techniques such as file truncation or sparse files to progressively shrink the archive size
50%UnverifiedThe RAR format (Roshal Archive) was developed by Eugene Roshal in 1993.
50%