Forem: Auth0

Things Developers Get Wrong About the Backend for Frontend Pattern

Andrea Chiarelli — Fri, 24 Apr 2026 15:51:18 +0000

Since I published my overview of the Backend for Frontend (BFF) pattern, the questions I've received fall into surprisingly consistent patterns. The same misunderstandings come up again and again, from developers who genuinely want to build secure apps.

Most of these misconceptions aren't just academic. They lead teams to ship apps with real security gaps while believing they've done the right thing. Let me address the ones I see most often.

Why PKCE Isn't a Replacement for BFF

This is the one I encounter most, and it's the most consequential.

The OAuth working group deprecated the Implicit Grant for SPAs and recommended Authorization Code with PKCE as the replacement. That guidance is correct. In addition, OAuth 2.1 recommends PKCE for any client, not just SPAs. Somehow, many developers concluded that PKCE also addresses token storage security. It doesn't.

PKCE (Proof Key for Code Exchange) protects the authorization code in transit. It prevents an attacker who intercepts the authorization code from exchanging it for tokens. Valuable, but it solves only one step of the OAuth flow.

Once your app receives tokens, PKCE has done its job. It has nothing to say about where those tokens live in the browser or what happens if a Cross-Site Scripting (XSS) attack runs in your app's context. Tokens in localStorage, sessionStorage, or even JavaScript memory are all reachable by malicious scripts.

BFF solves a different problem: it keeps tokens out of the browser entirely. The BFF exchanges the authorization code for tokens and stores them server-side. The browser gets an HttpOnly session cookie. An XSS attack running in that browser can't steal what isn't there.

PKCE and BFF are complementary, not alternatives. If your threat model includes XSS (and for most apps, it should), PKCE alone isn't enough.

BFF Is Not Just a Proxy

In a couple of cases, I've reviewed architectures labeled as "BFF" that were actually reverse proxies forwarding requests (and tokens) to a backend. That's not a BFF.

The defining characteristic of a Backend for Frontend is that it acts as a confidential OAuth client. It holds a client secret. It handles the full OAuth flow, including token exchange. Most critically, tokens never leave the server.

A reverse proxy that forwards an Authorization header containing a bearer token is not a BFF. The token is still accessible to the browser. You've added a network hop without the security benefit.

The IETF OAuth 2.0 for Browser-Based Apps BCP actually distinguishes between a Token-Mediating Backend (a backend that obtains tokens and then forwards them to the frontend) and a proper BFF (where tokens are never passed to the frontend at all). These are different patterns with different security properties.

If your backend is passing tokens to the browser in any form, you haven't implemented BFF. You've implemented token mediation, which is better than nothing, but it's not the same thing.

No, Cookies Are Not Less Secure Than Tokens

This one has roots in a legitimate historical concern. Cookies have a complicated reputation: they've been misused, and Cross-Site Request Forgery (CSRF) attacks were a real problem before SameSite became standard. Some of the "don't use cookies" instinct also came from REST API orthodoxy, where stateless communication was treated as a design virtue.

But here's what modern reality looks like: an HttpOnly session cookie cannot be read by JavaScript. That means XSS attacks can't steal it directly. A JWT in localStorage can be read by any script running on your page.

The attack surface isn't symmetric. A CSRF attack using an HttpOnly cookie requires the attacker to trick a user into making a specific authenticated request from another origin. An XSS attack that steals a localStorage token gives the attacker full, direct access to call any API as that user, from anywhere, without any user interaction required.

With SameSite=Strict or SameSite=Lax, CSRF attacks against HttpOnly cookies are already difficult in most real-world scenarios. Add explicit CSRF tokens and they become practically infeasible.

HttpOnly cookies aren't immune to CSRF, but the attack surface is far smaller than XSS-based token theft. You're trading one attack vector (XSS-based token theft) for a different, more constrained one (CSRF). That trade is almost always worth making.

BFF Does Not Solve All Your Browser Auth Security Problems

BFF shifts the security boundary. It doesn't eliminate it.

When you adopt BFF, you trade the token theft problem (XSS can steal tokens from browser storage) for the session management problem (your BFF now manages sessions and those need to be secured properly). This is a good trade in most cases, but it comes with responsibilities that BFF doesn't automatically fulfill.

Things BFF does not handle on its own:

CSRF protection. Your BFF uses cookies, which means state-changing requests need CSRF protection. SameSite cookies help significantly, but this is still your responsibility to configure correctly.
Session invalidation. When a user logs out, you need to revoke the session server-side, not just clear the cookie client-side. If you don't, stolen session cookies remain valid until natural expiry.
Secure cookie configuration. Secure, HttpOnly, and the right SameSite setting are all required. Missing any of them weakens the pattern's security properties.
Authorization checks in your API. BFF protects the token in transit. It doesn't automatically secure your API endpoints. You still need proper authorization logic on the backend.

Don’t implement BFF and then relax your overall security posture, assuming the pattern covers everything. It doesn't. Treat it as one layer in a defense-in-depth approach.

You Don’t Need to Rewrite Your Entire Application

The assumption that teams must rewrite the entire application prevents them from adopting BFF even when they should.

The full vision of BFF, as Sam Newman originally described it, is a server tailored to the specific needs of one frontend. That can mean a significant rearchitecting effort. But you don't have to implement the full pattern at once to get the security benefits.

In practice, many teams introduce BFF incrementally. The most common path:

Add a lightweight backend (Node.js, Next.js server components, ASP.NET Core, Python, or whatever fits your stack) that handles the OAuth flow.
The BFF exchanges authorization codes for tokens, stores them server-side, and issues session cookies to the browser.
Your existing frontend continues making API calls, now using session cookies instead of bearer tokens.

Your existing backend APIs often don't change at all. You're inserting the BFF as the authentication layer, not replacing your entire architecture.

The incremental path is real, and the auth-focused version of BFF is where most of the security value lives anyway.

Start With the Threat Model

Before deciding whether to implement BFF, be honest about your app's threat model.

If your application handles sensitive data, if XSS is a credible risk (and it usually is, especially for apps loading third-party scripts or rendering user-generated content), or if you operate in a regulated industry, BFF is the right choice. The complexity cost is manageable and the security benefit is concrete.

If you're building a simple public-facing app with no sensitive user data and strong existing XSS defenses, a well-implemented SPA with PKCE and in-memory token storage may be acceptable.

The BFF pattern exists because the browser is a hostile environment for tokens. If that threat is real for your application (and you're the best judge of that) BFF addresses it in ways that PKCE and in-browser token handling simply can't.

From Backend Engineer to Building AI Infrastructure at a Startup

Carla Urrea Stabile — Wed, 22 Apr 2026 16:05:00 +0000

What does it look like to go from a six-person startup team to running the infrastructure behind 1,000+ AI models?

Matteo and I have known each other for over 10 years, but I realized I'd never actually asked him about his engineering journey in depth. I knew he was doing infrastructure work, but I didn't know the full story of how he got there. This conversation filled in a lot of gaps for me.

In Episode 4 of Making Software, I talked to Matteo Ferrando, Platform and Infra Engineer at fal.ai, about exactly that.

What we covered

The pivot that changed everything. The company didn't start as an AI company. Matteo talks about what the original product was, how the pivot happened, and why letting go of something that's working is one of the hardest things you'll do at a startup as an engineer.
How a backend engineer ends up doing infra. There was no "switch." Matteo explains the reality of early-stage startups where in the beginning, there's no database, no Kubernetes cluster, no nothing. You just build it.
A decision-making framework worth stealing. One-way doors vs. two-way doors. Simple concept, but it changes how you think about MVPs, technical debt, and when to actually invest in doing things "the right way."
Optimizing a routing layer from 100ms to 5ms. The use case that forced this is wild. I'll let Matteo tell that story.
Do you still need computer science fundamentals? We talked about AI coding tools, what they're great at, and a very specific failure mode that Matteo keeps seeing on his team.

A couple of things Matteo said that stuck with me

"I'm not obsessed about technical debt like many engineers are. It's fine to have technical debt and we'll get to it."

This resonated a lot with me. I think a lot of us carry guilt about tech debt like it's something we did wrong. Matteo's framing is different: it's not a problem until it's actually a problem. That shift in perspective is freeing.

"A mistake introduced by an AI that you prompted is still your mistake. You still have to understand what you're shipping."

This one hit. Especially right now, when so many of us are leaning on AI tools to write code faster. Faster is great, but Matteo makes a really compelling case for why "I didn't write it" is not an excuse. He shares a specific example from his team that I think every developer using AI tools needs to hear.

Final thoughts

Talking to Matteo reminded me that there's no clean, linear path in engineering. You don't go from "backend engineer" to "infra engineer" because you planned it. You get there because something needs to exist and you're the one who builds it. I think that's something a lot of us can relate to, especially if you've ever worked at a startup.

Have you ever had to build something way outside your comfort zone because no one else was going to? Let me know in the comments!

Listen to the full episode

Available on YouTube, Apple Podcasts, and Spotify.

Thanks for reading! 👋

How to Use Auth0 Agent Skills in Claude Code & AI Coding Assistants

Jessica Temporal — Mon, 06 Apr 2026 18:27:59 +0000

Tired of your AI coding assistant hallucinating APIs or writing insecure auth patterns? In this video, I'll show you how to use Auth0 Agent Skills to teach your AI assistant (like Claude Code or GitHub Copilot) how to implement Auth0 correctly. Say goodbye to XSS vulnerabilities and manual JWT decoding—ship production-ready, secure authentication from the start.

What You'll Learn

Why standard AI coding assistants struggle with secure authentication.
How to install Auth0 Agent Skills via NPX or Claude Code plugins.
The difference between Core Skills and SDK Skills (React, Next.js, etc.).
A side-by-side comparison of "hallucinated" code vs. secure Auth0 patterns.
How to implement production-ready auth in Next.js using Agent Skills.

Resources

📝 Read the full blog post
🛠️ Auth0 Documentation
💻 GitHub Repo

Auth0 MCP Server Extension for Gemini CLI

Jessica Temporal — Fri, 27 Mar 2026 11:00:00 +0000

The Auth0 MCP Server is now listed on the official Gemini CLI extensions page. This means the Auth0 MCP Server is now directly installable through Gemini CLI with one command, allowing you to authenticate to Auth0 directly from your Gemini CLI session and load tenant information automatically.

What the Auth0 MCP Server Extension Provides

The extension packages the Auth0 MCP Server for Gemini CLI and adds three integration layers:

Discoverability: Listed on geminicli.com/extensions, searchable by name, installable without manual configuration.

Authentication Commands: Built-in slash commands for Auth0 tenant management:

/auth0:init - Device authorization flow with tenant selection
/auth0:logout - Session termination
/auth0:session - Current authentication status

Context Injection: After authentication, Gemini gains your tenant information so the AI can query applications, APIs, connections, actions, and logs without requiring manual tenant specification in every prompt.

Installation and Setup

Install the extension:

gemini extensions install https://github.com/auth0/auth0-mcp-server

Once the command successfully finishes you should see a message stating Extension “Auth0” installed successfully:

Initialize the Auth0 MCP Server:

/auth0:init

Make sure to allow the command to run when prompted. The server will run automatically.

You'll authenticate via device code flow to select your tenant:

And confirm the permissions:

Once authenticated, you should see a message within Gemini saying the Auth0 MCP Server is configured and to restart Gemini CLI to see the changes:

Refresh the MCP server list with the following command:

/mcp refresh

Gemini now has Auth0 context. Ask: "show me my applications" and the AI will receive the structured information about your applications, which Gemini CLI will display as a structured tool call result:

And since Gemini now understands your tenant structure, existing configurations, and naming conventions, it can also show you the same information in a more readable format:

Why This Matters

Before this extension, using the Auth0 MCP Server with Gemini CLI required manual server configuration, environment variable setup, and custom initialization scripts. The extension collapses that into a single install command and three slash commands.

More importantly: context persistence. Once authenticated, every Gemini session knows your Auth0 environment. You're not re-explaining your tenant structure or copy-pasting app IDs. The AI assistant operates with the same tenant awareness you have.

This is the same Auth0 MCP Server that powers VS Code integrations, now packaged for Gemini CLI's extension model. Same capabilities, different CLI.

What's Next

The Auth0 MCP Server supports tenant management, application configuration, API setup, and log analysis. For implementation details and the full MCP Server feature set, see the list on GitHub here.

The extension is available now at geminicli.com/extensions. Install, authenticate, and start managing Auth0 tenants through natural language.

The Future of Coding is Communication, Not Just Code

Carla Urrea Stabile — Thu, 26 Mar 2026 14:31:00 +0000

We recently had a great conversation on the Making Software podcast with Bobby Tierney. Bobby is a Principal Architect at Okta and Auth0 who focuses on agentic security, AI governance, and the Model Context Protocol (MCP).
I have been feeling some "AI FOMO" lately because the industry is moving so quickly. Talking to Bobby helped me bridge the gap between the "vibes" of modern AI coding and the security standards we need as professional engineers.

Vibe Coding vs. Mission Critical Production: Bobby shared his perspective on where "vibe coding" fits into the software development life cycle and when it becomes a risky proposition for an enterprise. He explained why prototypes are a great way to explore a solution space even if you eventually throw them away.
Managing "YOLO Mode" with Sandboxing: We discussed the "YOLO mode" found in many AI tools and how engineers can use progressive security configurations to keep things under control. -** The Shift to Spec-Driven Development:** Bobby talked about moving away from probabilistic guesswork and toward "spec coding". He explained how to use tools like "skills" or "slash commands" to align an AI with your team's specific DNA and ways of working.
The "Confused Deputy" Problem: We touched on the security risks of AI agents and why you shouldn't just give them machine credentials to act on a user's behalf. Bobby highlighted the importance of finding the right intersection between what a user is allowed to do and what the AI is permitted to do.
The Changing Role of the Engineer: We explored how AI is shrinking the development life cycle and why communication might be the most valuable skill for a developer in the future. Bobby also shared how designers and PMs are starting to use these tools to contribute directly to codebases.

Final Thoughts

Bobby reminded me that while tools are changing, the core of engineering is still about requirements and making good decisions.

The age of AI is not about replacing engineers. It is about helping them. By being good communicators, teachers, and security-minded builders, we can use these amazing tools to make better, safer software.

What is your take on YOLO mode coding? Let me know in the comments! 🌱
If you want to hear more, check out the full episode: https://listen.casted.us/public/49/Making-Software-2b1cff7b

Common FAPI Misconceptions

Andrea Chiarelli — Fri, 20 Mar 2026 09:00:30 +0000

For some time now, I've been interested in FAPI from both an Identity practitioner's and a developer's perspective. I've written a few posts on this topic on the Auth0 blog and created a guide to FAPI with the support of colleagues who are much more experienced than I am. Surfing the web and talking to developers, however, I couldn't help but notice some misunderstandings about certain aspects of FAPI.

In this article, I'll summarize the most common and recurring ones.

Misconception 1: FAPI Is a New Protocol

FAPI is a security profile based on OAuth 2.1, it is not a new protocol, intended as an alternative to established standards like OAuth 2.0, SAML, or OpenID Connect (OIDC).

It acts as a prescriptive blueprint that defines exactly which OAuth 2.0 and OIDC extensions must be used and how they must be configured. While the core OAuth 2.0 specification (RFC 6749) is a flexible framework that provides a "toolbox" of flows and leaves security decisions to the implementer, FAPI removes this "dangerous flexibility" to ensure a secure-by-default posture.

Misconception 2: FAPI Is for Banks and Financial Organizations

The "F" in FAPI originally stood for "Financial," reflecting its initial goal to protect banking applications. However, the scope has expanded significantly. Today, FAPI is a general-purpose high-security profile for any industry handling sensitive, high-risk data. Major applications include:

E-Health: Protecting Patient Health Information (PHI) in standards like HL7 FHIR.
E-Signing: Securing the underlying API calls for legally binding digital signatures.
Government Services: Managing Personally Identifiable Information (PII) and government services.

Misconception 3: FAPI 2.0 Is an Incremental Update of FAPI 1.0

Some people mistakenly believe FAPI 2.0 is a minor version bump that maintains backward compatibility. This is incorrect. FAPI 2.0 is a complete redesign based on lessons learned from FAPI 1.0, specifically aimed at simplifying the developer experience.

A key change is the removal of the OpenID Connect Hybrid Flow used in FAPI 1.0 "Advanced," which required complex front-channel validations of ID Tokens. FAPI 2.0 replaces this with a hardened Authorization Code Flow where all tokens are delivered via the back-channel.

Misconception 4: OAuth 2.1 Makes FAPI Redundant

As OAuth 2.1 incorporates modern best practices like PKCE and the removal of the Implicit Flow, some wonder if FAPI 2.0 remains necessary. However, the difference between the two is significant.

OAuth 2.1 is a "Best Current Practice" consolidation for the general community, while FAPI 2.0 is a "high-security profile" that mandates features OAuth 2.1 only recommends. Crucially, FAPI 2.0 is built on a Formal Attacker Model, providing proof of security against specific threats that OAuth 2.1 does not formally address.

Misconception 5: You Can Use Any Type of Client with FAPI

Standard OAuth 2.0 allows for both public (e.g., mobile, browser-based) and confidential (server-side) clients. However, while FAPI 1.0 Baseline specification allows for public clients, FAPI 1.0 Advanced and FAPI 2.0 explicitly excludes support for them.

FAPI 2.0 focuses on confidential clients because they are capable of protecting a private key. This is the cornerstone of FAPI’s security model; a client cannot perform asymmetric authentication or prove possession of a sender-constrained token if it cannot keep its private key secure.

Misconception 6: You Can’t Use Public Clients with FAPI

As a consequence of the previous point, you may conclude that you can’t use public clients at all with FAPI. So, you can’t have mobile applications or SPAs in a FAPI-based system.

Actually, this is not entirely true. You can still have public clients in a FAPI context provided that they don’t manage ID and access tokens. For example, you can have a SPA if you are using an architectural pattern like the Backend for Frontend pattern.

Misconception 7: Pushed Authorization Requests Support Simply Shortens URLs

Developers often view Pushed Authorization Requests (PAR) as merely an optional optimization for long URLs. In reality, FAPI 2.0 makes PAR mandatory because it moves the entire authorization request from the risky environment of the browser to the secure back-channel.

Standard GET requests expose sensitive data (scopes, identifiers) to browser history, server logs, and Referer headers. PAR solves this by having the client POST parameters directly to the server, receiving an opaque request_uri in return. This ensures:

Confidentiality: Sensitive parameters are never in the URL.
Integrity: The server authenticates the request before the user is ever involved.
Reliability: It bypasses URL length limits that often break complex authorization requests.

Wrapping Up

The journey through the FAPI landscape often involves navigating a complex mix of technical details and outdated assumptions. As this article has shown, FAPI is far more than an obscure security framework for banks; it is a critical, mature security profile that strips away the risky flexibility of standard OAuth 2.0 to offer a secure foundation for any system handling high-value data.

From understanding that FAPI is a profile, not a new protocol, to recognizing the fundamental changes in FAPI 2.0 and its mandated use of features like Pushed Authorization Requests (PAR), a clear picture emerges. FAPI’s strict reliance on confidential clients and back-channel communications is a pragmatic response to known threat models, ensuring integrity and confidentiality where it matters most.

Embracing FAPI is not about adding unnecessary complexity. It is about adopting a proven security posture necessary for protecting assets in e-Health, e-Signing, government services, and beyond. By moving past these common misconceptions, organizations can leverage FAPI to build truly robust and compliant high-security applications.

Here is an infographic that summarizes the misconceptions discussed in this article. Keep it handy:

Demystifying OAuth Security: State vs. Nonce vs. PKCE

Jessica Temporal — Fri, 13 Mar 2026 16:17:44 +0000

Confused by the random strings in your OAuth URLs? You aren't alone. Many developers think state, nonce, and code_challenge (PKCE) are redundant—but skipping just one could leave your users' accounts wide open to attackers like "Eve." In this video, I'll break down why these three parameters are like three different locks on three different doors. We’ll look at real-world attack scenarios and show you exactly how each one keeps your app secure.

💡 What You’ll Learn:

The State Parameter: How to prevent Cross-Site Request Forgery ($CSRF$) attacks.
The Nonce Parameter: Why ID tokens need protection against Replay attacks.
PKCE (Proof Key for Code Exchange): Protecting mobile and single-page apps from Authorization Code Injection.
Implementation Strategy: Why you should use all three instead of picking just one.

🔗 Links:

If you enjoy this content and want to learn more about identity, security, and access management, subscribe to our channel!

Have a topic you'd like to see covered? Let us know if the comments below 👀

Secure a C# MCP Server with Auth0

Andrea Chiarelli — Fri, 13 Mar 2026 09:59:59 +0000

As the Model Context Protocol (MCP) gains traction, the transition from "localhost" experimentation to enterprise integration introduces a critical challenge: security. For developers building sophisticated integrations, treating every LLM request as an "admin" action is a significant risk.

Luckily, the MCP specification supports authorization based on OAuth 2.1. So, basically, to protect your MCP server, you have to treat it as a resource server with some extra challenges in case you want to share it publicly to a wide audience.

The .NET ecosystem can leverage the C# SDK for MCP to easily expose tools and resources to an AI-powered application. The SDK reached maturity recently supporting all the features defined by the specification, including security.

This article explores a practical implementation of a secured MCP server. You will walk through a sample project and learn how to:

Implement three distinct tools: one available for public consumption and two gated behind specific permission sets.
Make the protected MCP server available to an MCP client, such as VSCode, leveraging Dynamic Client Registration (DCR) supported by Auth0.

Why Protect an MCP Server?

In a standard local setup, the MCP server and the client often share the same security boundary. However, as soon as an MCP server is deployed as a shared service or connected to a multi-user LLM platform, that boundary shifts. Protecting the server becomes relevant for at least two reasons:

Preventing prompt injection escalation. If a tool allows an LLM to interact with internal databases or APIs, a malicious prompt could attempt to trick the model into executing commands it shouldn't. By implementing strict authorization checks at the server level, you provide a defense in depth strategy. Even if the LLM is convinced to call a restricted tool, the MCP server will reject the request because the underlying user context lacks the necessary permissions.
Resource isolation and multi-tenancy. Not every user interacting with an AI agent should have the same capabilities. For example, a junior developer might have access to a ReadDocumentation tool, but only a lead engineer should be able to trigger a DeployProduction tool. Without protection, the MCP server treats all requests as equal, which is unacceptable in any regulated or professional environment.

These reasons are what OAuth 2.1 support in the MCP specification aims to prevent. We will use it to protect a sample MCP server built with C# by integrating with Auth0.

To learn how Auth0 helps you secure MCP clients and servers, check out Auth for MCP. For a detailed explanation of authorization support in MCP, read the Authorization specification.

Build Your MCP Server in C

Let’s begin our exploration by implementing a very simple MCP server that we will later extend and secure using Auth0.

Prerequisites

The MCP server project we are going to implement requires the following:

.NET SDK 10 or later,
The C# SDK for MCP package,
An Auth0 account. If you don’t have it, sign up for free here.

Create the MCP Server

To create a simple MCP server, you can use the MCP server template project provided by Microsoft. Currently, the template is in preview, so you won’t find it in the builtin template set. You can download and install the package by running the following command in a terminal window:

dotnet new install Microsoft.McpServer.ProjectTemplates

Once you have downloaded the project template, you can create your MCP server project by running a command like the following:

dotnet new mcpserver -n AspNetCoreMcpServer -t remote

This command creates a new MCP server project named AspNetCoreMcpServer in a folder with the same name. The option -t remote specifies to create an MCP server based on HTTP transport, which leads to actually creating an ASP.NET Core application.

MCP servers can use stdio or HTTP as transport protocols. OAuth protection for MCP servers is only designed for HTTP-based MCP servers. See When Should You Use Authorization? for more information.

Explore the project

Let’s take a quick look at the project to understand its implementation.

Go to the project’s folder and open the Program.cs file. You should see the the following code:

//Program.cs

var builder = WebApplication.CreateBuilder(args);

// Add the MCP services: the transport to use (http) and the tools to register.
builder.Services
    .AddMcpServer()
    .WithHttpTransport()
    .WithTools<RandomNumberTools>();

var app = builder.Build();
app.MapMcp();

app.Run();

This is an ordinary .NET application that uses the MCP server service (AddMcpServer). This service uses the HTTP transport (WithHttpTransport) and exposes the tools implemented by the class RandomNumberTools (WithTools<RandomNumberTools>). The invocation of the MapMcp() method initializes the MCP server.

The C# SDK for MCP library takes charge of all the complexity of implementing the MCP protocol. You can stay focused on the tool implementation, which is pretty straightforward as well.

Open the RandomNumberTools.cs file in the Tools folder and take a look at the code:

//Tools/RandomNumberTools.cs

using System.ComponentModel;
using ModelContextProtocol.Server;

internal class RandomNumberTools
{
    [McpServerTool]
    [Description("Generates a random number between the specified minimum and maximum values.")]
    public int GetRandomNumber(
        [Description("Minimum value (inclusive)")] int min = 0,
        [Description("Maximum value (exclusive)")] int max = 100)
    {
        return Random.Shared.Next(min, max);
    }
}

You see a very simple class implementing the method GetRandomNumber(), which returns a random number within a range. The attribute McpServerTool marks the GetRandomNumber() method as an MCP tool. The Description attributes describe what the tool does and what its parameters mean, very important to let the LLM understand when and how to use it. In fact, clear descriptions of the tool's functionality help the LLM select the appropriate tool for a given task.

That’s all! Your MCP server is ready to run.

Test your MCP server

Since the MCP server we implemented is nothing more than an ASP.NET Core application, we can test it in several ways: you can use curl or the .http file automatically generated with the project. Or you can use the MCP Inspector.

We'll integrate our MCP server directly into an MCP client like VSCode. This will come in handy later when we implement some advanced features.

You can add your MCP server to VSCode by creating a .vscode folder in your project’s root folder, and adding an mcp.json file with the following JSON content:

//.vscode/mcp.json
{
  "servers": {
    "AspNetCoreMcpServer": {
      "url": "http://localhost:PORT",
      "type": "http"
    }
  },
  inputs": []
}

Make sure to replace the PORT placeholder with the port your MCP server listens to.

Look at alternative ways to add your MCP server to VSCode.

Once you have added your MCP server to VSCode, set its chat window to agent mode and ask to get a random number. You should be prompted to authorize the use of the tool as shown in the following screenshot:

After you authorize it, you will get a random number:

Cool! You have a new working MCP server in your VSCode instance!

Protect Your MCP Server

Now let's move on to the real focus of this article: protecting your MCP server from unauthorized access.

Define the tools to protect

Currently, anyone installing your MCP server can use its only tool, get_random_number. This tool is publicly accessible because there is no restriction on it. You will leave it so, but you will also add two new tools that will require some form of authorization.

Specifically, you will add a tool that gets the current state of a hypothetical system and another one that sets the state of this system. The system is fictitious, of course, but you can think of it as a kind of processor that can be found in different states.

To implement these tools, add a new file named SystemTools.cs to the Tools folder with the following code:

//Tools/SystemTools.cs

using System.ComponentModel;
using ModelContextProtocol.Server;

internal enum SystemState
{
    Ready,
    Waiting,
    Running,
    Stopped
}

internal class SystemTools
{
    private static readonly SystemState[] AllStates = Enum.GetValues<SystemState>();
    private static SystemState? _currentState;

    [McpServerTool]
    [Description("Returns the current state of the fictitious system. Possible states are: Ready, Waiting, Running, Stopped.")]
    public string GetSystemState()
    {
        _currentState ??= AllStates[Random.Shared.Next(AllStates.Length)];
        return _currentState.ToString()!;
    }

    [McpServerTool]
    [Description("Sets the current state of the fictitious system. Valid states are: Ready, Waiting, Running, Stopped.")]
    public string SetSystemState(
        [Description("The new state to set. Must be one of: Ready, Waiting, Running, Stopped.")] SystemState state)
    {
        _currentState = state;
        return $"System state set to '{_currentState}'.";
    }
}

You see that the tool GetSystemState() picks a random state the first time it is called and stores it into a private static variable, _currentState. Any subsequent call to the tool will return the value stored in that variable.

The tool SetSystemState() changes the value of the state stored in the _currentState variable.

You will protect these two new tools by requiring that the user has specific permissions to use each of them.

According to the MCP specification, your MCP server is nothing but a resource server in the context of OAuth, and VSCode is just an OAuth client. So actually all you are going to implement is a well-known scenario: you will use Auth0 as the authorization server, which will authenticate the user and provide the access token to the MCP client (VSCode) in order to access the tools exposed by your MCP server. The access token will include the required permissions to access the protected tools.

However, you may have a little concern now. You want to share your MCP server as a package that anyone can download and use in their VSCode instance. How can they register their VSCode instance with Auth0 as required for any OAuth client? Well, the MCP specification supports a few ways to do this. You will use Dynamic Client Registration (DCR), which allows an MCP client (VSCode) to self-register with the authorization server (Auth0). Be aware that DCR raises security concerns, as we will mention later.

Configure your Auth0 tenant

First of all, you need to configure Auth0 at the tenant level. In fact, you need to enable Dynamic Client Registration to allow MCP clients to register. You also need to enable Resource Parameter Compatibility Profile as required by the MCP specification.

Keep in mind that these are tenant level settings, which means they affect all the applications registered in that tenant.

To enable those settings, go to Settings on the left menu and then select the Advanced tab. Scroll down to the Settings section and enable the Dynamic Client Registration (DCR) and Resource Parameter Compatibility Profile toggles, as shown in the image below:

As mentioned before, you need to enable Dynamic Client Registration to allow VSCode to self-register with Auth0 the first time a user interacts with your MCP server. This allows any client to register with Auth0 with potential risks such as resource exhaustion or unauthorized access attempts. Read Register your MCP Client Application to learn more about the dangers of an open DCR endpoint and possible solutions.

Beyond the static registration of an MCP client, an alternative approach is based on Client ID Metadata Document (CIMD), a recent standard whose implementation is in progress.

In addition to the previous tenant-level settings, you also need to promote the connections the MCP clients will use to domain level. To this purpose, go to the Authentication menu item of your dashboard and select the connection to configure. For our current example, select the Username-Password-Authentication connection under Database, and scroll down until you see the setting Promote Connection to Domain Level. Enable it as shown below:

Great! You have prepared your Auth0 tenant for self-registrations of MCP clients.

Register your MCP Server

Now you need to register your MCP server.

As mentioned earlier, from the OAuth point of view, an MCP server is nothing but a resource server or API server. This means that you can register it with Auth0 as a standard API. The only requirement is to make sure to set your MCP server base URL as the audience. This is a requirement of the Protected Resource Metadata specification. So, in your case, if your MCP server listens to http://localhost:5678, use this URL as the audience.

Once you have created your API on the Auth0 dashboard, scroll down in the Settings tab to reach the Access Token Settings section. Here, select the RFC 9068 format as shown in the following picture:

Read the documentation to learn more about access token profiles.

Then scroll down more to the RBAC Settings section and enable both RBAC and Add Permissions in the Access Token:

These settings will include the user’s permissions in the access token so your MCP server will be able to make authorization decisions to let users access the tools.

Save the settings and go to the Permissions tab. Here you should add the tool:getsystemstate and tool:setsystemstate permissions as shown below:

Follow the instructions in this document to learn how to add permissions to an API.

Finally, go to the Application Access tab and select the Allow value for the application access policy for user access, as you can see in the picture below:

This setting allows any self-registered MCP client to access your MCP server on behalf of the user. To learn more about this setting, read the API Access Policy documentation.

Now your MCP server is configured on the Auth0 side.

Secure your MCP Server

Let's complete the MCP server protection by modifying the current code.

First, add an appsettings.json file with the current content:

//appsettings.json

{
  "Auth0": {
    "Domain": "YOUR_DOMAIN",
    "Audience": "YOUR_MCP_SERVER_BASE_URL"
  },
  "McpServer": {
    "BaseUrl": "YOUR_MCP_SERVER_BASE_URL"
  }
}

Replace YOUR_DOMAIN with your Auth0 tenant domain, and YOUR_MCP_SERVER_BASE_URL with the actual URL of your MCP server. Remember that YOUR_MCP_SERVER_BASE_URL must also correspond to the audience you registered in Auth0.

Now you will add support for the access token validation and protection on the two MCP tools you added to the initial project.

Install the middleware to manage JWT tokens with the following command:

dotnet package add Microsoft.AspNetCore.Authentication.JwtBearer

Replace the current content of the Program.cs file with the following code:

//Program.cs
using Microsoft.AspNetCore.Authentication.JwtBearer;
using Microsoft.IdentityModel.Tokens;
using ModelContextProtocol.AspNetCore.Authentication;

var builder = WebApplication.CreateBuilder(args);

var authority = $"https://{builder.Configuration["Auth0:Domain"]}/";
var audience = builder.Configuration["Auth0:Audience"];
var mcpServerBaseUrl = builder.Configuration["McpServer:BaseUrl"];

builder.Services.AddAuthentication(options =>
{
    options.DefaultChallengeScheme = McpAuthenticationDefaults.AuthenticationScheme;
    options.DefaultAuthenticateScheme = JwtBearerDefaults.AuthenticationScheme;
})
.AddJwtBearer(options =>
{
    options.Authority = authority;
    options.TokenValidationParameters = new TokenValidationParameters
    {
        ValidateIssuer = true,
        ValidateAudience = true,
        ValidateLifetime = true,
        ValidateIssuerSigningKey = true,
        ValidAudience = audience,
        ValidIssuer = authority
    };

    options.Events = new JwtBearerEvents
    {
        OnTokenValidated = context =>
        {
            Console.WriteLine("Token validated successfully.");
            return Task.CompletedTask;
        },
        OnAuthenticationFailed = context =>
        {
            Console.WriteLine($"Authentication failed: {context.Exception.Message}");
            return Task.CompletedTask;
        }
    };
})
.AddMcp(options =>
{
    options.ResourceMetadata = new()
    {
        Resource = mcpServerBaseUrl ?? audience ?? string.Empty,
        AuthorizationServers = { authority },
        ScopesSupported = ["tool:getsystemstate", "tool:setsystemstate"],
    };
});

builder.Services.AddAuthorization();

builder.Services
    .AddMcpServer()
    .WithHttpTransport()
    .AddAuthorizationFilters()
    .WithTools<RandomNumberTools>();

var app = builder.Build();

app.MapMcp().RequireAuthorization();

app.Run(mcpServerBaseUrl);

Let’s break down this code to understand what it does.

Basically, it adds support for authenticating client requests as in any ordinary ASP.NET Core Web API:

//Program.cs

//...existing code...

builder.Services.AddAuthentication(options =>
{
    options.DefaultChallengeScheme = McpAuthenticationDefaults.AuthenticationScheme;
    options.DefaultAuthenticateScheme = JwtBearerDefaults.AuthenticationScheme;
})
.AddJwtBearer(options =>
{
    options.Authority = authority;
    options.TokenValidationParameters = new TokenValidationParameters
    {
        ValidateIssuer = true,
        ValidateAudience = true,
        ValidateLifetime = true,
        ValidateIssuerSigningKey = true,
        ValidAudience = audience,
        ValidIssuer = authority
    };

    options.Events = new JwtBearerEvents
    {
        OnTokenValidated = context =>
        {
            Console.WriteLine("Token validated successfully.");
            return Task.CompletedTask;
        },
        OnAuthenticationFailed = context =>
        {
            Console.WriteLine($"Authentication failed: {context.Exception.Message}");
            return Task.CompletedTask;
        }
    };
})

//...existing code...

This code sets up the access token validation logic through AddJwtBearer(). The OnTokenValidated and OnAuthenticationFailed event managers do nothing special apart from showing their message to the console, but you can use them for any customization you may need.

Just after AddJwtBearer() invocation, you find AddMcp(), as highlighted below:

//Program.cs

//...existing code...

builder.Services.AddAuthentication(options =>
{
  //...existing code...
})
.AddJwtBearer(options =>
{
  //...existing code...
})
.AddMcp(options =>
{
    options.ResourceMetadata = new()
    {
        Resource = mcpServerBaseUrl ?? audience ?? string.Empty,
        AuthorizationServers = { authority },
        ScopesSupported = ["tool:getsystemstate", "tool:setsystemstate"],
    };
});

//...existing code

The AddMcp() method defines the Protected Resource Metadata (PRM) document for this MCP server. This document provides useful information for the client about the capabilities of the MCP server and which authorization server to contact to access protected tools.

This document will be dynamically exposed at the URL YOUR_MCP_SERVER_BASE_URL/.well-known/oauth-protected-resource, where YOUR_MCP_SERVER_BASE_URL is the base URL of your MCP server. The document will contain the following JSON:

{
  "resource": "YOUR_MCP_SERVER_BASE_URL",
  "authorization_servers": [
    "https://YOUR_DOMAIN"
  ],
  "bearer_methods_supported": [
    "header"
  ],
  "scopes_supported": [
    "tool:getsystemstate",
    "tool:setsystemstate"
  ]
}

Finally, enforce authorization with the code highlighted below:

//Program.cs

//...existing code...

builder.Services.AddAuthorization();  //👈 new code

builder.Services
    .AddMcpServer()
    .WithHttpTransport()
    .AddAuthorizationFilters()  //👈 new code
    .WithTools<RandomNumberTools>();

var app = builder.Build();

app.MapMcp().RequireAuthorization();  //👈 changed code

app.Run(mcpServerBaseUrl);  //👈 changed code

You added the authorization middleware service (AddAuthorization()) and support for authorization filters (AddAuthorizationFilters()). Also, you applied authorization to the MCP endpoints (RequireAuthorization()) and forced the server to use the base URL defined in the appsettings.json file. The last change is not strictly required, but it ensures that you have one source of truth for the MCP base URL.

Add authorization policy

You added a generic support for authorization with AddAuthorization(). This makes sure that only authenticated users access the protected tools. But our initial intent is to allow users to access each specific tool based on their permissions.

You can do this by defining a couple of authorization policies based on the existence of specific permissions in the access token. To this purpose, replace the AddAuthorization() invocation with the following code:

//Program.cs

//...existing code...

builder.Services.AddAuthorization(options =>
{
    options.AddPolicy("GetSystemStatePolicy", policy =>
        policy.RequireClaim("permissions", "tool:getsystemstate"));

    options.AddPolicy("SetSystemStatePolicy", policy =>
        policy.RequireClaim("permissions", "tool:setsystemstate"));
});

//...existing code...

This code defines two authorization policies:

GetSystemStatePolicy based on the tool:getsystemstate value for the claim permissions.
SetSystemStatePolicy based on the tool:setsystemstate value for the claim permissions.

Let’s complete the protection of the tools by applying the authorization filter with the specific policy, as shown below:

//Tools/SystemTools.cs

//...existing code...

internal class SystemTools
{
    //...existing code...

    [McpServerTool]
    [Description("Returns the current state of the fictitious system. Possible states are: Ready, Waiting, Running, Stopped.")]
    [Authorize(Policy = "GetSystemStatePolicy")]  //👈 new code
    public string GetSystemState()
    {
        //...existing code...
    }

    [McpServerTool]
    [Description("Sets the current state of the fictitious system. Valid states are: Ready, Waiting, Running, Stopped.")]
    [Authorize(Policy = "SetSystemStatePolicy")]  //👈 new code
    public string SetSystemState(
        [Description("The new state to set. Must be one of: Ready, Waiting, Running, Stopped.")] SystemState state)
    {
        //...existing code...
    }
}

Your MCP server is secure now!

Test Your Secure MCP Server

Now it’s time to test your brand new secure MCP server!

Run your server with the dotnet run command.

Then, in your VSCode instance, restart your MCP server:

After a few seconds, you will see a popup message like the following:

This message is the effect of the RequireAuthorization() execution you added to the server. It sent a 401 HTTP status message to VSCode with a reference to the Protected Resource Metadata document, where VSCode found all the needed info to start the user authentication and authorization process.

Once you have allowed the authentication flow, you will get the authorization request that VSCode is about to send to Auth0, as shown below:

After user authentication, you will be requested to authorize VSCode to access your profile:

Once you accept the request, you will be redirected back to your VSCode instance.

You didn’t notice it, but under the hood, your VSCode instance automatically registered with Auth0 using DCR. You can verify this by going to your Auth0 dashboard and look in the list of the registered applications. You will see VSCode among them, and it is marked as a third-party application, as you can see below:

Now your VSCode instance has an access token to access the tools implemented by your MCP server.

Make sure your chat window is in Agent mode and list the tools provided by your MCP server. You will see only the get_random_number tool:

Why? Doesn’t VSCode have an access token?

VSCode has an access token, but without the required permissions to access the protected tools. So you can only access the public tool as before the protection implementation.

To test your MCP server properly, you should assign one or more of the required permissions to your user profile on Auth0. Follow the instructions in Assign Permissions to Users to assign the tool:getsystemstate permission to your user profile.

Use the command palette to sign out and restart your MCP server in VSCode. Then authenticate and check again the list of tools available to you. This time you should also see the get_system_state tool:

Ask something involving the state of the fictitious system in the chat window, as shown in the following screenshot:

You should be able to use the tool as expected.

Now, feel free to play with the permissions to get access to the other tool.

Let’s Recap

After a long journey, this article provided a comprehensive guide on securing a C# MCP server using Auth0, transforming it from a local experiment into an enterprise-ready resource server.

The journey covered the following main steps:

Building the Base MCP Server: You quickly set up a basic, unsecured MCP server using the C# SDK for MCP and the MCP server template, exposing a simple GetRandomNumber() tool.
Defining Protected Tools: You introduced two new tools, GetSystemState() and SetSystemState(), which require specific authorization, setting the stage for security implementation.
Auth0 Tenant Configuration: You configured the Auth0 tenant by enabling Dynamic Client Registration (DCR) to allow MCP clients (like VSCode) to self-register, and enabling the Resource Parameter Compatibility Profile as required by the MCP specification. We also promoted necessary connections to the domain level.
Registering the MCP Server as an API: The MCP server was registered with Auth0 as a standard API (Resource Server), ensuring its base URL was set as the audience. You configured it to use RFC 9068 access tokens and enabled Role-Based Access Control (RBAC) to include permissions in the access token.
Securing the Server Code: You updated the C# application to:
- Include necessary configuration via appsettings.json.
- Integrate the JwtBearer authentication middleware for access token validation against Auth0.
- Define the Protected Resource Metadata (PRM) document using AddMcp(), providing clients with authorization server and scope information.
- Implement authorization policies based on specific permissions.
- Apply these policies to the respective tools using the [Authorize] attribute.
Testing the Secure Server: Finally, you tested the secured server by integrating it with VSCode. The process demonstrated the DCR flow, user authentication, and the crucial step of assigning user permissions within Auth0 to grant access to the newly protected tools.

By following these steps, you successfully implemented an OAuth 2.1-compliant security layer, ensuring that access to sensitive tools is gated by proper user permissions validated through Auth0.

You can download the final version of this project from this GitHub repository, looking into the auth-for-mcp/aspnetcore-mcp-server folder.

To learn more about using Auth0 to secure your AI agents check out Auth0 for AI Agents.

The four-year-old typo that nobody can fix 🧟 and more about building developer tools

Carla Urrea Stabile — Wed, 25 Feb 2026 14:30:00 +0000

As the host of Making Software I get to have some pretty real conversations about what it actually takes to build good software. And in my recent chat with Raghd Hamzeh (Senior Software Engineer at Okta and a core maintainer of OpenFGA) hit home for me.

We talked about a side of engineering that doesn’t get enough airtime: what happens when your users are other engineers? If you’ve ever built an API, an SDK, or even just a shared library, you know that developers are the most rewarding, but also the most "vocal" audience you can have.

Here are the three things from our conversation that have been living rent-free in my head:

1. The "Breaking Change" Itch is Real 😬

Raghd admitted something that I think a lot of us can relate to: when there’s a four-year-old typo in one of the products you're building, that drives you crazy. It could be just a small naming inconsistency, but when it’s there, it's staring back at you every time.

We got into that internal battle every maintainer knows: do you break everyone’s build just to satisfy the need for a clean API? Probably not. But it’s a powerful reminder that the decisions we make in Month 1, like how we pass a parameter, become the legacy we have to live with in Year 5.

2. Stop building "Alien" SDKs 👽

This one got personal! While coding on the Ruby SDK for OpenFGA, I ran into this head-on. Rubyists are opinionated (I should know, I’m one of them).

When you’re building multi-language tools, you’re constantly balancing two things:

Consistency: Making sure the Go SDK and the Python SDK behave the same way.
Idiom: Making sure a Ruby dev doesn't feel like they're writing Java code with extra steps.

Raghd’s take? You won't get it perfect 100% of the time. Sometimes, you have to prioritize the long-term health of the platform over a "perfectly idiomatic" implementation just so the project stays maintainable for the team behind it. That tension never fully goes away, you just get better at navigating it.

3. The "AI" file that’s actually for humans 🤖

With the rise of AI, everyone is adding agents.md files to their repos. Raghd had a spicy take: Write that file for your human contributors first.

If you want people to help you build your open-source dream, lay out your expectations clearly:

How should commits be structured?
What does the core architecture look like?
Should contributors open an issue before submitting a PR?

Documenting these "non-code" decisions up front saves an enormous amount of friction. It turns "This PR isn't what we wanted" into "Here is the blueprint we’re all following."

🎙️ Want the full story?

Check out the full episode of Making Software here: Link to episode

I’d love to hear from you in the comments, what’s the one tiny thing in your codebase that you’re dying to "breaking change" just to feel better? 😅

Strengthening OAuth 2.0 with FAPI 2.0

Andrea Chiarelli — Tue, 24 Feb 2026 08:27:26 +0000

OAuth 2.0 has long been the cornerstone of modern authorization. It is a consolidated technology that powers everything from social logins to complex enterprise integrations. Developers appreciate its flexibility, which allows them to adapt the framework to various scenarios like traditional web applications, single page applications, desktop and mobile environments.

However, this flexibility is a double-edged sword. Because OAuth 2.0 is a framework rather than a rigid protocol, it provides a collection of specifications that developers can combine in different ways. In high-risk and regulated sectors like banking, healthcare, and insurance, this freedom creates a significant surface area for configuration errors and interoperability issues. This is where the FAPI profile steps in, providing a strict set of rules to ensure the highest levels of security and trust.

The Flexibility Paradox of OAuth 2.0

The fundamental challenge with "vanilla" OAuth 2.0 is the vast number of optional features. While the core specification defines the basic grant types, it leaves many security decisions to the implementer. For a developer building a low-risk internal tool, these choices are manageable. But for an architect designing a system for Open Banking or sensitive patient records, the stakes are much higher.

In high-assurance environments, the phrase "with great power comes great responsibility" applies literally. Security vulnerabilities often arise not from flaws in the individual specifications, but from how they are combined. For example, a system might use the Authorization Code Flow but fail to implement Proof Key for Code Exchange (PKCE) or use insecure redirect URIs. FAPI 2.0 solves this by removing the "optional" from security best practices and mandating a "secure by default" posture.

What Is FAPI 2.0?

FAPI 2.0 is a security profile developed by the OpenID Foundation. Unlike its predecessor (FAPI 1.0), which was often criticized for its complexity, FAPI 2.0 focuses on simplicity and robust interoperability. It is not a new protocol. Instead, it is a prescriptive profile that defines exactly which OAuth 2.0 and OpenID Connect extensions must be used and how they must be configured.

The profile is built upon a formal attacker model that assumes a high-threat environment where attackers might control the network or have the ability to intercept front-channel messages. By adhering to FAPI 2.0, organizations ensure their authorization servers and clients meet a standardized level of resistance against modern attack vectors like session injection, token theft, and authorization request tampering.

Hardening OAuth 2.0

The key security enhancements introduced by FAPI 2.0 to strengthen the OAuth 2.0 framework focus on three main areas: hardening the authorization request, eliminating bearer token risks, and improving client authentication. Here are the most relevant protection mechanisms FAPI 2.0 enforces:

Pushed Authorization Requests (PAR): FAPI 2.0 mandates PAR to mitigate the risks of sending sensitive authorization parameters (like scopes and PKCE challenges) over the insecure front-channel (browser). With PAR, the client sends these parameters via a secure back-channel POST request before redirection. The server then issues a short-lived request_uri used in the subsequent browser redirect, ensuring sensitive data never appears in browser history or logs.
Sender-Constrained Tokens: FAPI 2.0 moves away from vulnerable bearer tokens by enforcing "sender-constrained" tokens, which are cryptographically bound to the client that requested them. This prevents token misuse even if stolen. The primary mechanisms for this are Mutual TLS (mTLS), which binds the token to the client's X.509 certificate, and Demonstration of Proof-of-Possession (DPoP), a more flexible, application-level solution where the client proves possession of a private key using a signed JWT with every request.
Asymmetric Client Authentication: FAPI 2.0 replaces shared client secrets with asymmetric authentication, typically using Private Key JWT. The client signs a JWT with its private key, which the authorization server verifies with the client's registered public key. This method removes the risk of client secrets being leaked during transmission.

The Role of FAPI Certification

A critical component of the FAPI ecosystem is the OpenID Foundation's certification program. Because security depends on correct implementation, the foundation provides a suite of automated tests that vendors and organizations can use to verify their compliance. This certification provides a common ground for interoperability, ensuring that a FAPI-compliant client from one vendor can work seamlessly and securely with a FAPI-compliant authorization server from another.

Choosing certified components reduces the burden of security auditing and provides assurance that the system adheres to the industry's highest standards.

References and Further Reading

For more technical details on the specifications mentioned, consult the following official resources:

To learn more about FAPI 2.0 from a developer’s perspective, download the free ebook A Developer’s Guide to FAPI, which provides a detailed overview of the various security measures to make your application FAPI-ready.

Why Your Demo Code Should Be Treated as Production Code (And Other DevRel Secrets) 🎸

Carla Urrea Stabile — Thu, 29 Jan 2026 10:38:56 +0000

Have you ever found a code snippet in a tutorial, spent an hour trying to make it work, only to realize it’s using a deprecated library from 2019?

We’ve all been there.

I recently sat down with Sam Bellen, Principal Developer Advocate at Auth0, for the first episode of the Making Software podcast. We talked about the "diplomatic" nature of Developer Relations, the controversy of "selling" to developers, and why we need to stop treating demo code like a second-class citizen.

Here are the key takeaways for every developer, whether you’re looking to break into DevRel or just want to build better software.

1. DevRel: Part Engineer, Part Diplomat 🤝

Sam and I agreed on a unique definition: DevRel is a mix of developer and diplomat.

As a developer, you’re used to talking to Product Teams to understand requirements. In DevRel, that flow often reverses. You are the "voice of the developer" inside the company.

"It’s building relationships with the product teams... at a certain point, they will start trusting that what you’re telling them is actually valuable feedback instead of just randomly pinging people on Slack." — Sam Bellen

The Lesson: If you want to influence a product's roadmap, don't just throw bugs over the fence. Build a relationship with the people making the product. Trust is the currency of influence.

2. Authenticity > Sales 🚫💰

Developers are notoriously skeptical of being "sold" to. We can smell a marketing pitch from a mile away. Sam’s approach? Lead with the problem, not the product.

Instead of saying, "Use our auth tool because it's great," talk about how hard it is to implement DPoP (Demonstrating Proof-of-Possession) or Passkeys manually.

When you illustrate the complexity of a problem, the solution (your product) becomes a natural part of the conversation rather than a forced advertisement.

3. Treat Demo Code as Production Code 🛠️

This was Sam’s biggest take: Any code you write (even a tiny sample for a blog post) should be treated as production code.

If a vulnerability is found in a framework, DevRel teams should be the first to update their samples. Why? Because that sample is often a developer's first "touchpoint" with your tech.

Why this matters:

Security: Developers often copy-paste samples directly into their projects.
Trust: If your "Quick Start" doesn't work out of the box, you've lost the user.
Maintenance: Technical debt exists in docs, too. Set aside time (Sam recommends monthly) to audit your repos for deprecated APIs.

4. Get Your Hands Dirty with the Spec 📖

Sam has a "superpower": he actually likes reading technical specifications. While most of us fall asleep reading an RFC, Sam uses them to build visual tools that explain what’s happening "under the hood."

"In order for me to explain something... I build it myself. Not a clone of the product, but a demo that implements the topic. I make loads of mistakes, get lots of errors, and eventually, I figure out what's happening."

The "Aha!" Moment: You don't truly understand a tool until you've tried to build the logic it simplifies.

Summary: Two Steps to Better Developer Experience

If you’re an engineer looking to improve the DX (Developer Experience) of your project today, start here:

Listen to your DevRel team: They aren't just "social developers." They have the technical baggage and the community feedback to tell you what’s actually broken.
Stop "dropping" code on GitHub: Don't just create a repo and ignore it. If it’s public, it’s "production" for someone else.

🎧 Listen to the Full Episode

Want to hear the full conversation about guitars, Passkeys, and the early days of DevRel?

Listen to the full episode here or in your platform of choice.

What’s your take? Should demo code be held to the same linting and security standards as the core product? Let’s talk in the comments! 👇

Auth0 for AI Agents is now generally available!

Jessica Temporal — Mon, 24 Nov 2025 16:32:18 +0000

Hey DEV Community! 👋

If you're building AI agents right now (and honestly, who isn't?), you've probably hit the auth problem. You know the one - where the quickest path to getting your agent working is to just hardcode some API keys and move on. It works great... until you need to actually ship to production.

Today, we're excited to share that Auth0 for AI Agents is now generally available, and it's designed to solve exactly this problem.

Auth0 for AI Agents

The Problem with Hardcoded Credentials

Let's be real: when you're prototyping an AI agent with LangChain or LlamaIndex, hardcoded credentials are the path of least resistance. Your agent needs to access Slack, GitHub, Google Calendar, or your own APIs, and frameworks make it easy to just plug in those keys.

But production is a different story:

What happens when your agent needs to act on behalf of different users with different permissions?
How do you handle token refreshing across 30+ different apps?
How do you let users approve critical actions (like making purchases) without giving your agent carte blanche?
How do you ensure your RAG-powered agent only accesses documents the user actually has permission to see?

These aren't edge cases - they're fundamental requirements for any AI agent that's going to interact with real user data and take real actions.

What We Built

Auth0 for AI Agents gives you four key capabilities:

1. User Authentication

Secure and scalable User Authentication allows you to identify who's talking to your agent and give it secure access to your first-party APIs. Your agent can access user-specific data like order history, preferences, or chat logs - all scoped to the right permissions.

2. Token Vault

Token Vault handles OAuth flows with 30+ pre-integrated apps (GitHub, Slack, Google Workspace, and more) plus any custom OAuth provider you want to connect. It manages access tokens, refresh tokens, and the whole lifecycle automatically. Your agent requests a connection, the user authorizes once, and you never have to think about token management again.

The SDK detects when a tool call needs authentication, pauses execution, prompts the user to authenticate, stores the token securely, and resumes automatically. On subsequent calls, it just works.

3. Asynchronous Authorization

Your agent can work in the background and only interrupt the user when it needs approval for critical actions. Using Client-Initiated Backchannel Authentication (CIBA), you can send approval requests via email or Auth0 Guardian (SMS coming soon).

4. FGA for RAG

When your agent uses Retrieval Augmented Generation to search through documents, it needs to respect access controls. Fine-Grained Authorization for RAG ensures that users only get answers from documents they actually have permission to access.

Why This Matters

AI agents are moving from demos to production. The difference between a hackathon project and a real product often comes down to handling auth correctly. We built Auth0 for AI Agents because we kept hearing from developers that this was the hard part - not the LLM integration, not the prompt engineering, but the secure, user-scoped access to real systems.

This isn't about adding features. It's about removing blockers so you can ship production-ready AI agents without building your own auth infrastructure from scratch.

Framework Support

We've built SDKs for the frameworks you're already using:

LangChain (Python & JavaScript)
LlamaIndex (Python & JavaScript)
Cloudflare AI
Firebase Genkit
Vercel AI SDK

Each SDK handles the OAuth dance automatically, so you can focus on building your agent's capabilities, not wrestling with authentication flows.

Get Started

Our free tier includes two connected apps in Token Vault, async authorization, and all the core features you need to start building. As you scale, we have self-service plans that grow with you.

Early-stage startups can apply for one year of Auth0 free.

Start Building Today