Komga

Tested Versions

Before You Begin

You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it’s completely up to you.

This example makes the following assumptions:

  • Application Root URL: https://komga.example.com
  • Authelia Root URL: https://auth.example.com
  • Client ID: komga
  • Client Secret: komga_client_secret

Configuration

Application

To configure Komga to utilize Authelia as an OpenID Connect Provider:

  1. Configure the security section of the Komga configuration:
komga:
  ## Comment if you don't want automatic account creation.
  oauth2-account-creation: true
spring:
  security:
    oauth2:
      client:
        registration:
          authelia:
            client-id: `komga`
            client-secret: `komga_client_secret`
            client-name: Authelia
            scope: openid,profile,email
            authorization-grant-type: authorization_code
            redirect-uri: "{baseScheme}://{baseHost}{basePort}{basePath}/login/oauth2/code/authelia"
        provider:
          authelia:
            issuer-uri: https://auth.example.com
            user-name-attribute: preferred_username

Authelia

The following YAML configuration is an example Authelia client configuration for use with Komga which will operate with the above example:

- id: komga
  description: Komga
  secret: komga_client_secret
  public: false
  authorization_policy: two_factor
  redirect_uris:
    - https://komga.example.com/login/oauth2/code/authelia
  scopes:
    - openid
    - profile
    - email
  grant_types:
    - authorization_code
  userinfo_signing_algorithm: none

See Also