<?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-11">
   <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="February" day="17" 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
   for a resource server to signal to a client that the authentication
   event associated with the access token of the current request doesn&#x27;t
   meet its authentication requirements and specify 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-11" />
   
</reference>
