feat: add public URL endpoint and update user type to include password status

documentation/docs/configuration/social_auth.md

@@ -0,0 +1,15 @@
+# Social Authentication
+
+AdventureLog support autentication via 3rd party services and self-hosted identity providers. Once these services are enabled, users can log in to AdventureLog using their accounts from these services and link exising AdventureLog accounts to these services for easier access.
+
+The steps for each service varies so please refer to the specific service's documentation for more information.
+
+## Supported Services
+
+- [Authentik](social_auth/authentik.md) (self-hosted)
+- [GitHub](social_auth/github.md)
+- [Open ID Connect](social_auth/oidc.md)
+
+## Linking Existing Accounts
+
+If you already have an AdventureLog account and would like to link it to a 3rd party service, you can do so by logging in to AdventureLog and navigating to the `Account Settings` page. From there, scroll down to `Social and OIDC Authentication` and click the `Launch Account Connections` button. If identity providers have been enabled on your instance, you will see a list of available services to link to.

documentation/docs/configuration/social_auth/authentik.md

@@ -0,0 +1,52 @@
+# Authentik Social Authentication
+
+<img src="https://repository-images.githubusercontent.com/230885748/19f01d00-8e26-11eb-9a14-cf0d28a1b68d" alt="Authentik Logo" width="400" />
+
+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](https://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
+
+1. Log in to Authentik and navigate to the `Providers` page and create a new provider.
+2. Select `OAuth2/OpenID Provider` as the provider type.
+3. Name it `AdventureLog` or any other name you prefer.
+4. Set the `Redirect URI` of type `Regex` to `^http://<adventurelog-server-url>/accounts/oidc/.*$` where `<adventurelog-url>` is the URL of your AdventureLog Server service.
+5. Copy the `Client ID` and `Client Secret` generated by Authentik, you will need these to configure AdventureLog.
+6. Create an application in Authentik and assign the provider to it, name the `slug` `adventurelog` or any other name you prefer.
+
+### AdventureLog Configuration
+
+This configuration is done in the [Admin Panel](../../guides/admin_panel.md). You can either launch the pannel directly from the `Settings` page or navigate to `/admin` on your AdventureLog server.
+
+1. Login to AdventureLog as an administrator and navigate to the `Settings` page.
+2. Scroll down to the `Administration Settings` and launch the admin panel.
+3. 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: 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)
+
+   ```json
+   {
+     "server_url": "http://<authentik_url>/application/o/[YOUR_SLUG]/"
+   }
+   ```
+
+   - 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
+
+![Authentik Social Auth Configuration](/authentik_settings.png)
+
+4. 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.