Visual RFC.
ALL RFCs / RFC 8252
Read the RFC ↗
RFC 8252 / NATIVE-APP AUTHORIZATION

Claimed HTTPS callbacks

04

The operating system can associate a domain’s HTTPS links with its verified app.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 7.2 ↗
RFC 8252 · § 7.2EXAMPLE
3 / 3
Claimed HTTPS callbacksThe operating system can associate a domain’s HTTPS links with its verified app. Current state: Deliver the response to the associated app..Claimed HTTPS callbackshttps://app.example/callbackoperating-system URI dispatchAppverified associationdomain association
03
Deliver the response to the associated app.

The app checks its transaction and exchanges the code.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

Prefer app-claimed HTTPS where available.

  • Native apps SHOULD use claimed HTTPS callbacks over other options when possible.
  • The OS associates the destination domain with the application.
  • An HTTPS redirect does not make the installed app a confidential client; registration must still record the type.
DETAILS

These callbacks reduce interception risk, but the public client still needs PKCE.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Leave login to the browser
  2. A browser round trip, protected by PKCE
  3. Private-use callback schemes
  4. Claimed HTTPS callbacks
  5. Loopback callbacks on desktop
  6. Register the full callback
  7. Bind the response to the app’s request
  8. Fake browsers and client impersonation
  9. Server support and implicit-flow limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗