<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Firebase-Auth on CSP Guide</title>
    <link>https://csp-guide.com/tags/firebase-auth/</link>
    <description>Recent content in Firebase-Auth on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/firebase-auth/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Firebase Auth UI: Hosted UI vs Custom Flow</title>
      <link>https://csp-guide.com/posts/csp-for-firebase-auth-ui/</link>
      <pubDate>Fri, 10 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-firebase-auth-ui/</guid>
      
      <description>&lt;p&gt;Firebase Auth looks deceptively simple until you turn on a strict Content Security Policy.&lt;/p&gt;
&lt;p&gt;That’s where things usually go sideways: popups stop working, redirect flows break, reCAPTCHA refuses to load, and suddenly your clean &lt;code&gt;default-src &#39;self&#39;&lt;/code&gt; policy turns into a pile of Google domains and exceptions. I’ve seen teams spend more time debugging CSP around auth than building auth itself.&lt;/p&gt;
&lt;p&gt;If you’re using Firebase Auth UI, you’ve basically got two paths:&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
