---
title: Integrate with Wekan
sidebar_label: Wekan
support_level: community
---

## What is Wekan

> Wekan is an open-source kanban board which allows a card-based task and to-do management.
>
> -- https://github.com/wekan/wekan/wiki

## Preparation

The following placeholders are used in this guide:

- `wekan.company` is the FQDN of the wekan installation.
- `authentik.company` is the FQDN of the authentik installation.

:::note
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 Wekan 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 **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.
- **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**,**Client Secret**, and **slug** values because they will be required later.
    - Set a `Strict` redirect URI to <kbd>https://<em>wekan.company</em>/\_oauth/oidc</kbd>.
    - Select any available signing key.
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (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.

## Wekan configuration

import TabItem from "@theme/TabItem";
import Tabs from "@theme/Tabs";

<Tabs
  defaultValue="docker"
  values={[
    {label: 'Docker', value: 'docker'},
    {label: 'Standalone', value: 'standalone'},
  ]}>
  <TabItem value="docker">
If your Wekan is running in docker, add the following environment variables for authentik

```yaml
environment: OAUTH2_ENABLED=true
    OAUTH2_LOGIN_STYLE=redirect
    OAUTH2_CLIENT_ID=<Client ID from above>
    OAUTH2_SERVER_URL=https://authentik.company
    OAUTH2_AUTH_ENDPOINT=/application/o/authorize/
    OAUTH2_USERINFO_ENDPOINT=/application/o/userinfo/
    OAUTH2_TOKEN_ENDPOINT=/application/o/token/
    OAUTH2_SECRET=<Client Secret from above>
    OAUTH2_ID_MAP=sub
    OAUTH2_USERNAME_MAP=email
    OAUTH2_FULLNAME_MAP=given_name
    OAUTH2_EMAIL_MAP=email
```

  </TabItem>
  <TabItem value="standalone">

edit `.env` and add the following:

```ini
     # authentik OAUTH Config
      OAUTH2_ENABLED='true'
      OAUTH2_LOGIN_STYLE='redirect'
      OAUTH2_CLIENT_ID='<Client ID from above>'
      OAUTH2_SERVER_URL='https://authentik.company'
      OAUTH2_AUTH_ENDPOINT='/application/o/authorize/'
      OAUTH2_USERINFO_ENDPOINT='/application/o/userinfo/'
      OAUTH2_TOKEN_ENDPOINT='/application/o/token/'
      OAUTH2_SECRET='<Client Secret from above>'
      OAUTH2_ID_MAP='sub'
      OAUTH2_USERNAME_MAP='email'
      OAUTH2_FULLNAME_MAP='given_name'
      OAUTH2_EMAIL_MAP='email'
```

  </TabItem>
</Tabs>
