authelia

2.5 KiB

Raw Blame History

title

description

lead

date

draft

images

weight

toc

community

Komga

Integrating Komga with the Authelia OpenID Connect Provider.

2022-08-26T11:39:00+10:00

false

integration

parent
openid-connect

620

true

Tested Versions

Authelia
- v4.36.4
Komga
- v0.157.1

Before You Begin

Assumptions

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: insecure_secret

Configuration

Application

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

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: `insecure_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: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_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

2.5 KiB Raw Blame History