From a508dd8d9600e73bfed63c7053978b1ecc0bbad2 Mon Sep 17 00:00:00 2001 From: Corbin Whitton Date: Fri, 17 Jan 2025 15:55:31 -0700 Subject: [PATCH] update documentation for authentik --- .../docs/configuration/social_auth/authentik.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/documentation/docs/configuration/social_auth/authentik.md b/documentation/docs/configuration/social_auth/authentik.md index 6bc62d9..6d86ed8 100644 --- a/documentation/docs/configuration/social_auth/authentik.md +++ b/documentation/docs/configuration/social_auth/authentik.md @@ -54,3 +54,13 @@ This configuration is done in the [Admin Panel](../../guides/admin_panel.md). Yo 4. Save the configuration. 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. + +## Troubleshooting + +### 404 error when logging in. + +Ensure the /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 AdventureLog 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 AdventureLog application.