authentik/website/integrations/networking/technitium/index.md

title, sidebar_label, support_level

title	sidebar_label	support_level
Integrate with Technitium DNS	Technitium DNS	community

import RedirectURI20265Note from "../../_redirect-uri-2026-5-note.mdx";

What is Technitium DNS?

Technitium DNS Server is a free, open source, cross-platform, authoritative and recursive DNS server that can be self-hosted for privacy and security, software development, and testing on small to medium-sized networks.

-- https://technitium.com/dns/

Preparation

The following placeholders are used in this guide:

• technitium.company is the FQDN of the Technitium DNS installation.
• authentik.company is the FQDN of the authentik installation.

This guide requires Technitium DNS Server version 15.0 or later.

:::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 Technitium DNS with authentik, you need to create a scope mapping, an application/provider pair, and application entitlements in authentik.

Create a scope mapping in authentik

Technitium DNS uses the roles claim to map SSO users to local groups. Create a scope mapping to pass authentik application entitlements as role values.

1. Log in to authentik as an administrator and open the authentik Admin interface.

2. Navigate to Customization > Property Mappings and click Create.

   • Select type: select Scope Mapping.

   • Configure the Scope Mapping: configure the following settings:

     • Name: provide a descriptive name, such as Technitium DNS roles.
     • Scope name: profile
     • Expression:

     return {
         "roles": [
             entitlement.name
             for entitlement in request.user.app_entitlements(provider.application)
         ],
     }
     

3. Click Finish to save the scope mapping.

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. Note the slug value because it will be required later.
   • 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.
     • Add a Redirect URI of type Strict Authorization as https://technitium.company/sso/callback.
     • Select any available signing key.
     • Ensure that the openid, email, and profile scopes are selected. Remove the email scope if you prefer usernames to use the preferred username claim instead of the email address; if you do this, remove the email scope from Technitium in the next section.
     • Under Advanced protocol settings > Selected Scopes, add the scope mapping that you created in the previous section.
   • Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's Application Dashboard page.

3. Click Submit to save the new application and provider.

Create application entitlements in authentik

Use application entitlements to represent the Technitium DNS groups that this application should assign.

1. Open the Technitium DNS application that you just created in the authentik Admin interface.
2. Click the Application entitlements tab.
3. Create one entitlement for each Technitium DNS group that users should be able to receive, such as Technitium Admins.
4. Expand each entitlement and click Bind existing group/user to bind the users or groups that should receive it.

:::tip Entitlement group names The entitlement names must exactly match the Remote Group values that you configure in the Technitium Group Map. :::

Technitium configuration

1. Log in to the Technitium web console using a local administrator account.
2. Navigate to Administration > Single Sign-On (SSO).
3. Select Enable Single Sign-On (SSO).
4. Configure the following settings:
   • Authority (Issuer): https://authentik.company/application/o/<application_slug>/
   • Client ID: enter the client ID from authentik.
   • Client Secret: enter the client secret from authentik.
5. If you removed the email scope from the authentik provider, remove email from the Technitium Scopes list.
6. Configure SSO User Sign Up as appropriate:
   • Allow New User Sign Up: enable this to allow automatic provisioning of user accounts for new SSO users.
   • Allow Sign Up Only For Mapped Users: enable this to restrict sign-up to users that belong to a mapped remote group. If enabled, you must configure at least one entry in the Group Map section, otherwise new SSO users cannot sign up.
7. Configure the Group Map to map authentik application entitlements to local Technitium groups:
   • Remote Group: the name of the authentik application entitlement (e.g. Technitium Admins).
   • Local Group: the corresponding Technitium local group (e.g. Administrators).

:::warning Local administrator fallback It is strongly recommended to keep a local administrator account as a fallback. Any DNS failure could cause SSO to stop working, making it impossible for SSO-only users to log in. :::

8. Click Save Config to apply the changes. The web service restarts automatically.

Configuration verification

To confirm that authentik is properly configured with Technitium DNS, log out of Technitium. Then, navigate to the Technitium login page and click OpenID Connect. You should be redirected to authentik to log in, and if successful, redirected to the Technitium dashboard.

Resources

• Technitium DNS Server v15 release announcement
• Technitium DNS Server API documentation
• Technitium DNS Server Docker environment variables