2022-08-26 01:39:00 +00:00
---
title: "Komga"
description: "Integrating Komga with the Authelia OpenID Connect Provider."
lead: ""
2022-09-01 02:24:47 +00:00
date: 2022-08-26T11:39:00+10:00
2022-08-26 01:39:00 +00:00
draft: false
images: []
menu:
integration:
parent: "openid-connect"
weight: 620
toc: true
community: true
---
## Tested Versions
* [Authelia]
* [v4.36.4 ](https://github.com/authelia/authelia/releases/tag/v4.36.4 )
2022-08-26 03:26:58 +00:00
* [Komga]
2022-08-26 01:39:00 +00:00
* [v0.157.1 ](https://github.com/gotson/komga/releases/tag/v0.157.1 )
## Before You Begin
2023-02-02 01:30:06 +00:00
{{% oidc-common %}}
2022-10-20 04:42:22 +00:00
2022-10-20 04:27:09 +00:00
### Assumptions
2022-08-26 01:39:00 +00:00
This example makes the following assumptions:
* __Application Root URL:__ `https://komga.example.com`
* __Authelia Root URL:__ `https://auth.example.com`
2022-08-26 03:26:58 +00:00
* __Client ID:__ `komga`
2023-02-02 01:30:06 +00:00
* __Client Secret:__ `insecure_secret`
2022-08-26 01:39:00 +00:00
## Configuration
### Application
2023-01-25 23:59:18 +00:00
To configure [Komga] to utilize Authelia as an [OpenID Connect 1.0] Provider:
2022-08-26 01:39:00 +00:00
2022-08-26 03:26:58 +00:00
1. Configure the security section of the [Komga] configuration:
```yaml
komga:
## Comment if you don't want automatic account creation.
oauth2-account-creation: true
spring:
2022-08-26 01:39:00 +00:00
security:
oauth2:
client:
registration:
authelia:
2023-05-07 06:39:17 +00:00
client-id: 'komga'
client-secret: 'insecure_secret'
client-name: 'Authelia'
scope: 'openid,profile,email'
authorization-grant-type: 'authorization_code'
2022-08-26 01:39:00 +00:00
redirect-uri: "{baseScheme}://{baseHost}{basePort}{basePath}/login/oauth2/code/authelia"
provider:
authelia:
2023-05-07 06:39:17 +00:00
issuer-uri: 'https://auth.example.com'
user-name-attribute: 'preferred_username'
2022-08-26 01:39:00 +00:00
````
### Authelia
The following YAML configuration is an example __Authelia__
2023-05-15 00:32:10 +00:00
[client configuration ](../../../configuration/identity-providers/openid-connect/clients.md ) for use with [Komga]
2022-08-26 01:39:00 +00:00
which will operate with the above example:
```yaml
2023-04-02 03:12:01 +00:00
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
2023-05-07 06:39:17 +00:00
- id: 'komga'
description: 'Komga'
2023-04-02 03:12:01 +00:00
secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
2023-05-07 06:39:17 +00:00
authorization_policy: 'two_factor'
2023-04-02 03:12:01 +00:00
redirect_uris:
2023-05-07 06:39:17 +00:00
- 'https://komga.example.com/login/oauth2/code/authelia'
2023-04-02 03:12:01 +00:00
scopes:
2023-05-07 06:39:17 +00:00
- 'openid'
- 'profile'
- 'email'
2023-04-02 03:12:01 +00:00
grant_types:
2023-05-07 06:39:17 +00:00
- 'authorization_code'
2023-05-15 00:32:10 +00:00
userinfo_signing_alg: 'none'
2022-08-26 01:39:00 +00:00
```
## See Also
2022-08-26 03:26:58 +00:00
* [Komga Configuration options Documentation ](https://komga.org/installation/configuration.html )
2022-08-26 01:39:00 +00:00
* [Komga Social login Documentation ](https://komga.org/installation/oauth2.html )
[Authelia]: https://www.authelia.com
[Komga]: https://www.komga.org
2023-01-25 23:59:18 +00:00
[OpenID Connect 1.0]: ../../openid-connect/introduction.md