<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-oauth-browser-based-apps" target="https://datatracker.ietf.org/doc/html/draft-ietf-oauth-browser-based-apps-22">
   <front>
      <title>OAuth 2.0 for Browser-Based Applications</title>
      <author initials="A." surname="Parecki" fullname="Aaron Parecki">
         <organization>Okta</organization>
      </author>
      <author initials="D." surname="Waite" fullname="David Waite">
         <organization>Ping Identity</organization>
      </author>
      <author initials="P." surname="De Ryck" fullname="Philippe De Ryck">
         <organization>Pragmatic Web Security</organization>
      </author>
      <date month="January" day="17" year="2025" />
      <abstract>
	 <t>   This specification details the threats, attack consequences, security
   considerations and best practices that must be taken into account
   when developing browser-based applications that use OAuth 2.0.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the Web Authorization
   Protocol Working Group mailing list (oauth@ietf.org), which is
   archived at https://mailarchive.ietf.org/arch/browse/oauth/.

   Source for this draft and an issue tracker can be found at
   https://github.com/oauth-wg/oauth-browser-based-apps.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-oauth-browser-based-apps-22" />
   
</reference>
