Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions website/integrations/services/tailscale/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,15 +25,15 @@ Use this JSON template for your WebFinger response:
{
"links": [
{
"href": "https://authentik.company",
"href": "https://authentik.company/application/o/tailscale/",
"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.
**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. Replace `tailscale` with the actual slug used in the application configuration below.
:::

:::note
Expand All @@ -49,7 +49,7 @@ To support the integration of Tailscale with authentik, you need to create an ap
1. Log in to authentik as an administrator and open the authentik Admin interface.
2. Navigate to **Applications** > **Applications** and click **Create with Provider** to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.)

- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
- **Application**: provide a descriptive name, slug (used in the WebFinger JSON template) 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.
Expand Down