2.7 KiB
Authentik Social Authentication
Authentik is a self-hosted identity provider that supports OpenID Connect and OAuth2. AdventureLog can be configured to use Authentik as an identity provider for social authentication. Learn more about Authentik at goauthentik.io.
Once Authentik is configured by the administrator, users can log in to AdventureLog using their Authentik account and link existing AdventureLog accounts to Authentik for easier access.
Configuration
To enable Authentik as an identity provider, the administrator must first configure Authentik to allow AdventureLog to authenticate users.
Authentik Configuration
- Log in to Authentik and navigate to the
Providerspage and create a new provider. - Select
OAuth2/OpenID Provideras the provider type. - Name it
AdventureLogor any other name you prefer. - Set the
Redirect URIof typeRegexto^http://<adventurelog-server-url>/accounts/oidc/.*$where<adventurelog-url>is the URL of your AdventureLog Server service. - Copy the
Client IDandClient Secretgenerated by Authentik, you will need these to configure AdventureLog. - Create an application in Authentik and assign the provider to it, name the
slugadventurelogor any other name you prefer.
AdventureLog Configuration
This configuration is done in the Admin Panel. You can either launch the pannel directly from the Settings page or navigate to /admin on your AdventureLog server.
-
Login to AdventureLog as an administrator and navigate to the
Settingspage. -
Scroll down to the
Administration Settingsand launch the admin panel. -
In the admin panel, navigate to the
Social Accountssection and click the add button next toSocial applications. Fill in the following fields:- Provider:
OpenID Connect - Provider ID: Autnentik Client ID
- Name:
Authentik - Client ID: Authentik Client ID
- Secret Key: Authentik Client Secret
- Key: can be left blank
- Settings: (make sure http/https is set correctly)
{ "server_url": "http://<authentik_url>/application/o/[YOUR_SLUG]/" }- Sites: move over the sites you want to enable Authentik on, usually
example.comandwww.example.comunless you renamed your sites.
- Provider:
What it Should Look Like
- Save the configuration and restart the AdventureLog server.
Ensure that the Authentik server is running and accessible by AdventureLog. Users should now be able to log in to AdventureLog using their Authentik account.
