<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Access on vanityURLs</title><link>https://vanityurls.link/en/tags/access/</link><description>Recent content in Access on vanityURLs</description><generator>Hugo</generator><language>en-CA</language><lastBuildDate>Sun, 07 Jun 2026 18:08:29 -0400</lastBuildDate><atom:link href="https://vanityurls.link/en/tags/access/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloudflare Access is not a checkbox</title><link>https://vanityurls.link/en/blog/operating-cloudflare-access-for-a-short-link-domain/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://vanityurls.link/en/blog/operating-cloudflare-access-for-a-short-link-domain/</guid><description>&lt;p&gt;The failure mode is ordinary. Someone opens &lt;code&gt;/en/_stats/&lt;/code&gt; from a private browser window and sees the dashboard instead of the Cloudflare Access login page.&lt;/p&gt;
&lt;p&gt;That is the whole problem. Public redirects should stay public. Operational pages should not.&lt;/p&gt;
&lt;p&gt;For vanityURLs, &lt;a href="https://developers.cloudflare.com/cloudflare-one/applications/"&gt;Cloudflare Access&lt;/a&gt; has one narrow job: keep localized stats paths such as &lt;code&gt;/en/_stats/&lt;/code&gt;, localized test paths such as &lt;code&gt;/en/_tests/&lt;/code&gt;, and similar operator surfaces private before the Worker serves them. Treat it as an access boundary, not a setup souvenir.&lt;/p&gt;</description></item><item><title>Start with one-time PIN, then earn the IdP</title><link>https://vanityurls.link/en/blog/choosing-identity-provider/</link><pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate><guid>https://vanityurls.link/en/blog/choosing-identity-provider/</guid><description>&lt;p&gt;The first identity decision for a short-link domain should be boring.&lt;/p&gt;
&lt;p&gt;Protect &lt;code&gt;/en/_stats/&lt;/code&gt;, other localized stats paths, and &lt;code&gt;/en/_tests/&lt;/code&gt; before the instance goes public. Do not spend the first deploy designing an enterprise identity architecture unless the enterprise already exists.&lt;/p&gt;
&lt;p&gt;For vanityURLs, &lt;a href="https://developers.cloudflare.com/cloudflare-one/applications/"&gt;Cloudflare Access&lt;/a&gt; protects the operational pages before the Worker serves them. The question is not &amp;ldquo;which IdP is best?&amp;rdquo; The question is &amp;ldquo;which access path can the operator review and revoke without ceremony?&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>