<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-oauth-step-up-authn-challenge" target="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-step-up-authn-challenge-17">
   <front>
      <title>OAuth 2.0 Step Up Authentication Challenge Protocol</title>
      <author initials="V." surname="Bertocci" fullname="Vittorio Bertocci">
         <organization>Auth0/Okta</organization>
      </author>
      <author initials="B." surname="Campbell" fullname="Brian Campbell">
         <organization>Ping Identity</organization>
      </author>
      <date month="June" day="26" year="2023" />
      <abstract>
	 <t>It is not uncommon for resource servers to require different authentication strengths or recentness according to the characteristics of a request.  This document introduces a mechanism that resource servers can use to signal to a client that the authentication event associated with the access token of the current request does not meet its authentication requirements and, further, how to meet them.  This document also codifies a mechanism for a client to request that an authorization server achieve a specific authentication strength or recentness when processing an authorization request.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-oauth-step-up-authn-challenge-17" />
   
</reference>
