Signed-off-by: Amir Zarrinkafsh <3339418+nightah@users.noreply.github.com>
4.7 KiB
title, description, summary, date, draft, images, weight, toc, aliases, support, seo
| title | description | summary | date | draft | images | weight | toc | aliases | support | seo | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AdventureLog | Integrating AdventureLog with the Authelia OpenID Connect 1.0 Provider. | 2025-04-26T18:35:57+10:00 | false | 620 | true |
|
|
|
Tested Versions
{{< callout context="caution" title="Important Note" icon="outline/alert-triangle" >}} A bug with Adventure Log requires manual adjustments to this guide and those adjustments are noted. See #544 for more detail. {{< /callout >}}
{{% oidc-common %}}
Assumptions
This example makes the following assumptions:
- Application Root URL:
https://adventurelog.{{< sitevar name="domain" nojs="example.com" >}}/ - Authelia Root URL:
https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/ - Client ID:
adventurelog - Client Secret:
insecure_secret
Some of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
Configuration
Authelia
The following YAML configuration is an example Authelia client configuration for use with AdventureLog which will operate with the application example:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- client_id: 'adventurelog'
client_name: 'Adventure Log'
client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: 'two_factor'
require_pkce: false
pkce_challenge_method: ''
redirect_uris:
- 'https://adventurelog.{{< sitevar name="domain" nojs="example.com" >}}/accounts/oidc/authelia/login/callback/'
- 'https://adventurelog.{{< sitevar name="domain" nojs="example.com" >}}/accounts/oidc/adventurelog/login/callback/' # Note: this is the workaround redirect_uri.
scopes:
- 'openid'
- 'email'
- 'profile'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'client_secret_basic'
Application
To configure AdventureLog there is one method, using the Web GUI.
Web GUI
To configure AdventureLog to utilize Authelia as an OpenID Connect 1.0 Provider, use the following instructions:
- Login to AdventureLog.
- Navigate to the Admin Panel:
- Clicking your profile picture.
- Select Settings.
- Click Launch Admin Panel.
- Scroll down to Social Accounts.
- Under Social Applications, click Add.
- Configure the following options:
- Provider:
OpenID Connect - Provider ID:
authelia(Note: this will need to beadventureloguntil the bug is fixed) - Name:
Authelia - Client ID:
adventurelog - Secret Key:
insecure_secret - Settings:
{"server_url": "https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}"} - Sites: Select the sites you want to enable OpenID Connect for.
(By default, you should add the pre-created
example.comsite.)
- Provider:
- Press
Saveat the bottom.
Linking Existing Accounts
Users can manually link their accounts by:
- Click their profile picture.
- Select Settings.
- Select Launch Account Connections.
- Select Authelia.