<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Authentication on Nicolai Van der Storm</title><link>https://nvds.be/tags/authentication/</link><description>Recent content in Authentication on Nicolai Van der Storm</description><generator>Hugo</generator><language>en</language><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Thu, 07 May 2026 11:08:13 +0200</lastBuildDate><atom:link href="https://nvds.be/tags/authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>Seamless Auto-Authentication in Bruno API Client</title><link>https://nvds.be/posts/bruno-auto-auth/</link><pubDate>Thu, 07 May 2026 10:54:35 +0200</pubDate><guid>https://nvds.be/posts/bruno-auto-auth/</guid><description>&lt;h1 id="seamless-auto-authentication-in-bruno-api-client"&gt;Seamless Auto-Authentication in Bruno API Client&lt;/h1&gt;
&lt;p&gt;When building and testing APIs, token expiry is an annoying but unavoidable reality. If your tokens expire mid-session, you&amp;rsquo;re stuck manually re-logging in and re-running your requests. In this post I&amp;rsquo;ll walk through how I set up fully automatic token refresh in &lt;a href="https://www.usebruno.com/"&gt;Bruno&lt;/a&gt; no manual intervention needed.&lt;/p&gt;
&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;The naive approach to handling expired tokens is to catch 401 responses in a post-response script and retry the request. The issue? Bruno always displays the &lt;strong&gt;original&lt;/strong&gt; response in the UI there&amp;rsquo;s no way to replace it from a script. So even if your retry succeeds, you&amp;rsquo;re staring at a 401.&lt;/p&gt;</description></item></channel></rss>