Skip to main content

Integrate with Vikunja

Support level: Community

What is Vikunja?​

Vikunja is an Open-Source, self-hosted To-Do list application for all platforms.

-- https://vikunja.io/

Preparation​

The following placeholders are used in this guide:

  • vikunja.company is the FQDN of the Vikunja installation.
  • authentik.company is the FQDN of the authentik installation.
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​

Redirect URI changes in authentik 2026.5

In authentik versions earlier than 2026.5, all Redirect URIs are automatically treated as Authorization type. If you are using one of these older authentik versions, add only the Authorization URL to your Redirect URIs and do not configure a Post Logout URI.

To support the integration of Vikunja with authentik, you need to create an application/provider pair in authentik.

Create an application and provider​

  1. Log in to authentik as an administrator and open the authentik Admin interface.
  2. Navigate to Applications > Applications and click New Application 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, optional UI settings, and note the application 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.
      • For web login, add a Redirect URI of type Strict Authorization as https://vikunja.company/auth/openid/authentik.
      • If you use the Vikunja desktop client, add a Redirect URI of type Regex Authorization as ^http://127\\.0\\.0\\.1:[0-9]+/auth/openid/authentik$.
      • Select any available signing key.
    • 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.

Vikunja configuration​

Configure Vikunja using either a config file or environment variables. The provider key authentik in the examples below must match the final path segment in the redirect URI configured in authentik. If you choose a different provider key, use lowercase letters and no spaces, and update the redirect URI to /auth/openid/<provider_key>.

Set the following values in config.yml:

config.yml
auth:
    openid:
        enabled: true
        providers:
            authentik:
                name: "authentik Login"
                authurl: https://authentik.company/application/o/<application_slug>/
                clientid: <Client ID from authentik>
                clientsecret: <Client Secret from authentik>
                scope: openid email profile

To require SSO for all users, disable local authentication:

config.yml
auth:
    local:
        enabled: false

Restart Vikunja after applying the OpenID configuration.

Configuration verification​

To verify the integration with Vikunja, open Vikunja and click Log in with authentik Login. You should be redirected to authentik and then redirected back to Vikunja.

Resources​