Skip to main content

Authentication + authorization for Caddy

Who gets in?
You write the rules.

Connect identity, login, and access policies with AuthCrunch. Follow a request below, then build the same flow in Caddy.

Build your first setup Follow a request
A sign-in portal sends an identity through a glass access-policy gateway. Two applications are allowed; a third is denied.
Sign inCheck accessReach apps

Follow a request

Change the visitor. Change the rule. See the decision.GET /

01 / The visitor

Alice's roles
authp/userapp/member

02 / Caddy + AuthCrunch

Your access policy
allow roles authp/admin authp/user

03 / The decision

200 OK

The app is yours to use.

Alice has authp/user. The policy allows the request to reach the app.

An interactive illustration of the walkthrough’s access rules.Run it yourself

Your first working setup

Four steps. A working front door.​

Start the learning path
  1. Get the right buildInstall the ready-to-run Caddy distribution and verify its modules.Open the guide
  2. Make your first loginRun the local portal. Follow real screenshots through the login flow.Open the guide
  3. Connect identity to accessSee how the portal, cookies, and application policy fit together.Open the guide
  4. Prove your policy worksCheck allowed access, denied access, and the next request after logout.Open the guide

Explore the moving parts

What are you working on?​

Choose a part of the flow. Find the guides that move you forward.

Browse all guides

01 / Identity

Start with the people signing in.

Connect local users or an external identity provider. Understand which claims arrive before you grant access.

Explore identity guides

Choose the right starting point

Different apps.
Different ways to sign in.​

A portal with profile pages and a policy that signs users in directly have different responsibilities. Compare the flows before choosing yours.

Understand the login models

Authentication establishes identity.
Your policy decides what that identity may access.

Two ways to protect an app

  1. Sign in through the portalLocal users or an identity provider
  2. Receive an access tokenThe portal records the user's claims
  3. Check access to the appYour policy evaluates those claims

Use a portal for login, local MFA and profile pages. Attach an authorization policy to the protected app.

Understand the moving parts

Keep learning by doing

Start local. Follow the whole request.​

One Caddyfile, two demo users, and an application you can protect.

Start the walkthrough Something isn't working? Troubleshoot