<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Workos on CSP Guide</title>
    <link>https://csp-guide.com/tags/workos/</link>
    <description>Recent content in Workos on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 07 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/workos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for WorkOS Authentication</title>
      <link>https://csp-guide.com/posts/csp-for-workos-authentication/</link>
      <pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-workos-authentication/</guid>
      
      <description>&lt;p&gt;Content Security Policy gets awkward fast once authentication enters the picture.&lt;/p&gt;
&lt;p&gt;A basic app can survive on &lt;code&gt;default-src &#39;self&#39;&lt;/code&gt; and a couple of explicit allowlists. Then you add WorkOS authentication, maybe a hosted sign-in page, maybe social login redirects, maybe passkeys, and suddenly people start punching holes in the policy until the browser stops complaining.&lt;/p&gt;
&lt;p&gt;That usually works. It also usually leaves you with a CSP that looks secure but barely does anything.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
