<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OAuth on Nalar</title>
    <link>https://nalar.dev/tags/oauth/</link>
    <description>Recent content in OAuth on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/oauth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Match OAuth Redirect URIs Exactly</title>
      <link>https://nalar.dev/match-oauth-redirect-uris-exactly/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/match-oauth-redirect-uris-exactly/</guid>
      <description>&lt;p&gt;An OAuth authorization server eventually has to answer a deceptively simple question: &lt;strong&gt;where may it send the browser after authorization?&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;If that destination is validated too loosely, an authorization response intended for one client can be sent somewhere the client does not control. In an authorization-code flow, that can expose the authorization code to another endpoint. Other protections may still limit what can be done with a leaked code, but redirect validation should not create the leak in the first place.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
