Protect an ASP.NET Core API

Add OneiD to a .NET API API with Microsoft.AspNetCore.Authentication.JwtBearer, step by step.

View as Markdown

This quickstart adds OneiD to a api with Microsoft.AspNetCore.Authentication.JwtBearer. Every file is complete and runs as it is.

Tip Using an AI coding agent? Give it this page as Markdown (add .md to the address) together with the Connector specification. See Build with AI coding agents.

Before you start

  • A OneiD address, for example https://YOUR_ONEID. The code below uses the demonstration instance https://auth.oltinid.com; replace it with your own.
  • An access token with the scope orders.read to test with.

1. Register the application

An API is not a client: it does not sign in. It needs an API scope that clients can request.

  1. Ask your OneiD administrator to create the API scope orders.read (or a scope named after your API) in the admin console.
  2. Ask for the scope to be allowed on the client that will call the API.
  3. Get an access token with that scope: from a server or browser application, or with the client credentials grant.

Note OneiD access tokens have no aud claim. The API accepts a token because it was issued by your OneiD, is unexpired and carries the scope the API requires. Give each API its own scopes. See Protect an API.

2. Install

dotnet add package Microsoft.AspNetCore.Authentication.JwtBearer

3. Add the code

Program.cs

using System.Security.Claims;
using Microsoft.AspNetCore.Authentication.JwtBearer;

var builder = WebApplication.CreateBuilder(args);

builder.Services
    .AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
    .AddJwtBearer(options =>
    {
        // Reads the issuer name and signing keys from OneiD; checks the signature, issuer and expiry.
        options.Authority = "https://auth.oltinid.com";
        options.TokenValidationParameters.ValidateAudience = false; // OneiD tokens have no aud claim
        options.MapInboundClaims = false;                           // keep the claim names that OneiD sends
    });

builder.Services.AddAuthorization(options =>
{
    // The scope claim is one string with a space between the scopes.
    options.AddPolicy("orders.read", policy => policy.RequireAssertion(context =>
        context.User.FindFirst("scope")?.Value.Split(' ').Contains("orders.read") == true));
});

var app = builder.Build();
app.UseAuthentication();
app.UseAuthorization();

app.MapGet("/orders", (ClaimsPrincipal user) => new { sub = user.FindFirst("sub")?.Value })
    .RequireAuthorization("orders.read");

app.Run("http://localhost:4000");

4. Run it

Run: dotnet run.

The API listens on http://localhost:4000. GET /orders answers 401 without a valid token, 403 without the scope orders.read, and otherwise returns the sub of the caller.

Test it with a token:

curl -i http://localhost:4000/orders
# HTTP/1.1 401 Unauthorized

curl -i http://localhost:4000/orders -H "Authorization: Bearer $ACCESS_TOKEN"
# HTTP/1.1 200 OK when the token carries orders.read, 403 when it does not

Checkpoint Without a token the API answers 401. With a valid token that carries orders.read it answers 200 and returns your sub; with a valid token without that scope it answers 403.

Common issues

  • 401 with a token that looks valid. Check the issuer: OneiD’s issuer ends with a slash (https://YOUR_ONEID/).
  • The API checks aud and rejects every token. OneiD access tokens carry no aud; remove the audience check and check the scope instead.
  • More errors and fixes: Errors and troubleshooting.

Learn more