Files

alex df8d1adf15 Rename AdventureLog to Voyage and add fork attribution

- Replace all AdventureLog references with Voyage across ~102 files
  (7 case variants: AdventureLog, adventurelog, Adventurelog, ADVENTURELOG,
  AdventUrelog, AdventureLOG, adventure-log, adventure_log)
- Rename brand, static, and documentation assets to use voyage naming
- Rename install_adventurelog.sh → install_voyage.sh
- Update README.md and voyage_overview.md to credit AdventureLog as
  the upstream project and Sean Morley as its original creator

2026-03-06 11:05:26 +00:00

3.8 KiB

Raw Blame History

Authentik OIDC Authentication

Authentik is a self-hosted identity provider that supports OpenID Connect and OAuth2. Voyage 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 Voyage using their Authentik account and link existing Voyage accounts to Authentik for easier access.

Configuration

To enable Authentik as an identity provider, the administrator must first configure Authentik to allow Voyage to authenticate users.

Authentik Configuration

Log in to Authentik and navigate to the Providers page and create a new provider.
Select OAuth2/OpenID Provider as the provider type.
Name it Voyage or any other name you prefer.
Set the Redirect URI of type Regex to ^http://<voyage-server-url>/accounts/oidc/.*$ where <voyage-url> is the URL of your Voyage Server service.
Copy the Client ID and Client Secret generated by Authentik, you will need these to configure Voyage.
Create an application in Authentik and assign the provider to it, name the slug voyage or any other name you prefer.
If you want the logo, you can find it here.

Voyage Configuration

This configuration is done in the Admin Panel. You can either launch the panel directly from the Settings page or navigate to /admin on your Voyage server.

Login to Voyage as an administrator and navigate to the Settings page.
Scroll down to the Administration Settings and launch the admin panel.
In the admin panel, navigate to the Social Accounts section and click the add button next to Social applications. Fill in the following fields:
- Provider: OpenID Connect
- Provider ID: Authentik 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]/"
}
```
::: warning localhost is most likely not a valid server_url for Authentik in this instance because localhost is the server running Voyage, not Authentik. You should use the IP address of the server running Authentik or the domain name if you have one.

Sites: move over the sites you want to enable Authentik on, usually example.com and www.example.com unless you renamed your sites.

What it Should Look Like

Save the configuration.

Ensure that the Authentik server is running and accessible by Voyage. Users should now be able to log in to Voyage using their Authentik account.

Linking to Existing Account

If a user has an existing Voyage account and wants to link it to their Authentik account, they can do so by logging in to their Voyage account and navigating to the Settings page. There is a button that says Launch Account Connections, click that and then choose the provider to link to the existing account.

Troubleshooting

404 error when logging in.

Ensure the <voyage-server-url>/accounts path is routed to the backend, as it shouldn't hit the frontend when it's properly configured.

Authentik - No Permission

In the Authentik instance, check access to the Voyage application from a specific user by using the Check Access/Test button on the Application dashboard. If the user doesn't have access, you can add an existing user/group policy to give your specific user/group access to the Voyage application.

3.8 KiB Raw Blame History