a caddy plugin for authenticating via tailscale ACL grants
Files
README.md

Tailscale authentication in Caddy #

This is a plugin for the Caddy webserver that enables Tailscale-based authentication. It is a fork of this wonderful plugin, updated to support Tailscale's application capabilities via grants.

I am very grateful to the original plugin, which I have been using with success for a while now and without which this modified plugin would not exist.

Installation #

Add go.samasaur.com/caddy-tailscale-auth to your Caddy build

Example usage #

In your Caddyfile:

www.example.com {
    tailscale_auth samasaur.com/cap/caddy-tailscale
    reverse_proxy localhost:9000
}

In your Tailscale policy file:

{
    "grants": [
        {
            "src": ["group:admins"],
            "dst": ["my-server"],
            "ip": ["443"],
            "app": {
                "samasaur.com/cap/caddy-tailscale": [
                    {
                        "admin": true, // Grants access to all sites; false if omitted
                        "sites": {
                            "my-site.com": true, // Grants access to the given site; false if omitted
                            "my-other-site.com": true
                        },
                    }
                ],
            },
        },
    ]
}

The original README is reproduced below:


Tailscale authentication in Caddy #

This is a plugin for the Caddy webserver that enables Tailscale-based authentication. It functions similarly to the default basic_auth Caddyfile directive except using the local Tailscale daemon and the remote address of a connection to authenticate based on if a connection is coming via a Tailnet and if so, who it is.

Optionally, the Tailscale-User-{Id,Login,Name} headers are set on the incoming request to allow this to be used as an analogue for forward_auth. The names of these headers can be modified (see below).

Installation #

Add go.akpain.net/caddy-tailscale-auth to your Caddy build.

Limitations #

This module requires the Tailscale daemon to be running on the same machine as the Caddy server.

Example usage #

Require all incoming connections to be from within a Tailnet

www.example.com {
  tailscale_auth
  reverse_proxy localhost:9090
}

Require all incoming connections to be from within a Tailnet, setting headers

www.example.com {
  tailscale_auth set_headers
  reverse_proxy localhost:9090
}

Remap header names - there can be multiple remap lines in a block.

www.example.com {
  tailscale_auth set_headers {
    remap Tailscale-User-Login X-Authentik-Email
  }
  reverse_proxy localhost:9090
}

Allow only certain users by email address - there is not currently any way to do this without email addresses.

www.example.com {
  tailscale_auth {
    allowed_logins example@gmail.com
  }
  reverse_proxy localhost:9090
}