<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.zhu-oauth-async-delegation" target="https://datatracker.ietf.org/doc/html/draft-zhu-oauth-async-delegation-00">
   <front>
      <title>Sender-Constrained Delegation Handle for Asynchronous OAuth 2.0 Identity Chaining</title>
      <author initials="L." surname="Zhu" fullname="Larry Zhu">
         <organization>Atlassian</organization>
      </author>
      <author initials="S." surname="Currie" fullname="Sam Currie">
         <organization>Atlassian</organization>
      </author>
      <date month="May" day="22" year="2026" />
      <abstract>
	 <t>   This document defines an extension to OAuth 2.0 Token Exchange
   [RFC8693] and the OAuth Identity Chaining draft
   [I-D.ietf-oauth-identity-chaining] for delegated workflows that must
   continue after the end user has gone offline.  When a chained access
   token expires while the end user is unavailable to re-authenticate
   (for example, to satisfy a multi-factor authentication or a
   touch-to-engage gesture), the acting client today has no standards-
   defined way to obtain a refreshed chained token without either
   widening privileges, breaking the identity chain, or impersonating
   the user as a service.  This specification introduces the
   &quot;Delegation Handle&quot;: a sender-constrained, audience-locked, scope-
   frozen JSON Web Token issued by the authorization server alongside a
   chained access token, that the original acting client MAY present
   back to the authorization server to refresh the chained access token
   within strict, server-side policy bounds and without re-prompting
   the end user.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-zhu-oauth-async-delegation-00" />
   
</reference>
