mirror of
https://github.com/goauthentik/authentik
synced 2026-04-27 09:57:31 +02:00
6ed5cb5249
* website/integrations: rename "Create with Provider" to "New Application" The application list page now uses a split-button labeled "New Application" instead of the old "Create with Provider" dropdown. Update all 113 integration guides to match. * website/docs: update flow, stage, and policy button labels - "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons - "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit - "Create and bind stage" → "New Stage" / "Bind Existing Stage" - "Create" (binding submit) → "Create Stage Binding" * website/docs: update provider button labels - "Create" → "New Provider" for trigger buttons - "Create with Provider" → "New Application" in RAC docs - "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt" for related entity creation * website/docs: update directory button labels - "Create" → "New Source" for federation/social login pages - "Create" → "New Role", submit → "Create Role" - "Create" → "New Invitation" - Policy binding submit → "Create Policy Binding" * website/docs: update endpoint device and system management button labels - "Create" → "New Endpoint Connector", "New Enrollment Token", "New Device Access Group", "New Flow" - Submit → "Create Device Access Group" - "Create" → "New Notification Rule", "New Notification Transport" - Binding submit → "Create Policy Binding" * Reorganize policy documentation * website/docs: address policy docs review feedback * post-rebase * website/docs: Reorganize policy documentation -- Revisions (#21601) * apply suggestions * Fix escaped. * Fix whitespace. * Update button label. * Fix phrasing. * Fix phrasing. * Clean up stragglers. * Format. --------- Co-authored-by: Dominic R <dominic@sdko.org>
78 lines
3.6 KiB
Markdown
78 lines
3.6 KiB
Markdown
---
|
|
title: Integrate with Tailscale
|
|
sidebar_label: Tailscale
|
|
support_level: community
|
|
---
|
|
|
|
## What is Tailscale
|
|
|
|
> Tailscale is a mesh VPN service that creates secure, encrypted, peer-to-peer connections between devices across different networks using the WireGuard protocol.
|
|
>
|
|
> -- https://tailscale.com
|
|
|
|
## Preparation
|
|
|
|
The following placeholders are used in this guide:
|
|
|
|
- `authentik.company` is the FQDN of the authentik installation.
|
|
|
|
:::info
|
|
Tailscale requires a properly configured WebFinger endpoint at `.well-known/webfinger` on the domain used for your email. Set this up according to your web server or application specifications.
|
|
|
|
Use this JSON template for your WebFinger response:
|
|
|
|
```json
|
|
{
|
|
"links": [
|
|
{
|
|
"href": "https://authentik.company/application/o/<application_slug>/",
|
|
"rel": "http://openid.net/specs/connect/1.0/issuer"
|
|
}
|
|
],
|
|
"subject": "acct:your@email.com"
|
|
}
|
|
```
|
|
|
|
**Important:** Replace `your@email.com` with the administrator email that you will use when creating your Tailnet. The domain in the email address must match the domain where the WebFinger endpoint is served and the domain you will use for Tailscale.
|
|
:::
|
|
|
|
:::info
|
|
This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application.
|
|
:::
|
|
|
|
## authentik configuration
|
|
|
|
To support the integration of Tailscale with authentik, you need to create an application/provider pair in authentik.
|
|
|
|
### Create an application and provider in authentik
|
|
|
|
1. Log in to authentik as an administrator and open the authentik Admin interface.
|
|
2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard.
|
|
- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
|
|
- **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
|
|
- **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
|
|
- Note the **Client ID** and **Client Secret** values because they will be required later.
|
|
- Set a `Strict` redirect URI to `https://login.tailscale.com/a/oauth_response`.
|
|
- Select any available signing key.
|
|
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/bindings-overview/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.
|
|
|
|
3. Click **Submit** to save the new application and provider.
|
|
|
|
## Tailscale configuration
|
|
|
|
1. Visit [Tailscale's sign up page](https://login.tailscale.com/start) and click **Sign up with OIDC**.
|
|
2. Enter the administrator email, select `authentik` as the identity provider type, and click **Get OIDC Issuer**.
|
|
3. Set the following configurations:
|
|
- **Client ID**: enter the Client ID copied from authentik.
|
|
- **Client secret**: enter the Client secret copied from authentik.
|
|
- **Prompts**: keep the default value `consent`.
|
|
4. Click **Sign up with OIDC** and follow the prompts to complete the Tailscale-specific configuration.
|
|
|
|
## Configuration verification
|
|
|
|
To verify the integration with Tailscale, log out and attempt to log back in using an email address from your configured SSO domain. You should be redirected to your authentik instance and after successfully logging in, you should be redirected to the Tailscale dashboard.
|
|
|
|
## Resources
|
|
|
|
- [Tailscale SSO documentation](https://tailscale.com/kb/1240/sso-custom-oidc)
|