add references to gatus, freshrss, frappe; frappe new authentik confi…

…g format, freshrss revamp; fix typo in bookstack cfg

website/integrations/services/bookstack/index.mdx

@@ -98,7 +98,7 @@ In the authentik Admin Interface, navigate to **Applications** > **Applications*
     - Set the **Issuer** to <kbd>https://<em>authentik.company</em></kbd>.
     - Set the **Service Provider Binding** to `Post`.
     - Set the **Audience** to <kbd>https://<em>bookstack.company</em>/saml2/metadata</kbd>.
-    - Under **Advanced protocol settings**, set **Signing Certificate** to use any availible certificate.
+    - Under **Advanced protocol settings**, set **Signing Certificate** to use any available certificate.
 - **Configure Bindings** _(optional):_ you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user’s **My applications** page.
 
 **Obtain the SAML metadata URL**

website/integrations/services/frappe/index.md

@@ -31,12 +31,20 @@ This documentation only lists the settings that have been changed from their def
 
 ## authentik configuration
 
-1. From the **authentik Admin interface**, navigate to **Applications** -> **Applications**.
-2. Use the [wizard](https://docs.goauthentik.io/docs/add-secure-apps/applications/manage_apps#add-new-applications) to create a new application and a **OAuth2/OpenID Connect provider**. During this process:
+To support the integration of Frappe with authentik, you need to create an application/provider pair in authentik.
+
+**Create an application and provider in authentik**
+
+In the authentik Admin Interface, navigate to **Applications** > **Applications** and click **[Create with Provider](/docs/add-secure-apps/applications/manage_apps#add-new-applications)** to create an application and provider pair. (Alternatively, you can create only an application, without a provider, by clicking **Create**.)
+
+- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
+- **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
+- **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
     - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later.
     - Set a `Strict` redirect URI to <kbd>https://<em>frappe.company</em>/api/method/frappe.integrations.oauth2_logins.custom/provider</kbd>.
     - Select any available signing key.
     - Under **Advanced Protocol Settings**, set **Subject mode** to be `Based on the Users's username`.
+- **Configure Bindings** _(optional):_ you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user’s **My applications** page.
 
 ## Frappe configuration
 
@@ -46,7 +54,7 @@ This documentation only lists the settings that have been changed from their def
 
 2. **Add a New Social Login Key**
 
-    - Click the black **+ New** button in the top-right corner.  
+    - Click the black **+ New** button in the top-right corner.
       ![](./frappe1.png)
 
 3. **Enter the Required Settings**
@@ -59,7 +67,7 @@ This documentation only lists the settings that have been changed from their def
 
     - **Configuration**
 
-        - **Sign-ups**: Set to **Allow**.  
+        - **Sign-ups**: Set to **Allow**.
           ![](./frappe2.png)
 
     - **Identity Details**
@@ -69,7 +77,7 @@ This documentation only lists the settings that have been changed from their def
             - **Authorize URL**: `/application/o/authorize/`
             - **Access Token URL**: `/application/o/token/`
             - **Redirect URL**: <kbd>https://<em>frappe.company</em>/api/method/frappe.integrations.oauth2_logins.custom/provider</kbd>
-            - **API Endpoint**: `/application/o/userinfo/`  
+            - **API Endpoint**: `/application/o/userinfo/`
               ![](./frappe3.png)
 
     - **Client Information**
@@ -82,6 +90,10 @@ This documentation only lists the settings that have been changed from their def
 4. **Save the Configuration**
     - Click the black **Save** button in the top-right corner to complete the setup.
 
-## Verification
+## References
+
+- [Frappe's official OpenID Connect guide](https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login)
+
+## Configuration verification
 
-First, open an incognito browser window and go to `https://frappe.company`. On the login screen, click **Login with Provider**. You will be redirected to authentik to enter your credentials and to authorize the application. Once that's done, you will be redirected to the home screen of the Frappe application, confirming the successful login.
+To verify that authentik is correctly set up with Frappe, navigate to your Frappe installation and click **Login with Provider**. A successful login should redirect you to the main page of your installation.

website/integrations/services/freshrss/index.mdx

@@ -0,0 +1,77 @@
+---
+title: Integrate with FreshRSS
+sidebar_label: FreshRSS
+---
+
+import IntegrationsMultilineCodeblock from "@site/src/components/Integrations/IntegrationsCodeblock";
+
+# Integrate with FreshRSS
+
+<span class="badge badge--secondary">Support level: Community</span>
+
+## What is FreshRSS
+
+> FreshRSS is a self-hosted RSS feed aggregator.
+>
+> -- https://github.com/FreshRSS/FreshRSS
+
+## Preparation
+
+The following placeholders are used in this guide:
+
+- `freshrss.company` is the FQDN of the FreshRSS installation.
+- `authentik.company` is the FQDN of the authentik installation.
+
+:::note
+This documentation only lists the settings that have been changed from their default values. Please verify your changes carefully to avoid any issues accessing your application.
+:::
+
+## authentik configuration
+
+To support the integration of FreshRss with authentik, you need to create an application/provider pair in authentik.
+
+**Create an application and provider in authentik**
+
+In the authentik Admin Interface, navigate to **Applications** > **Applications** and click **[Create with Provider](/docs/add-secure-apps/applications/manage_apps#add-new-applications)** to create an application and provider pair. (Alternatively you can create only an application, without a provider, by clicking **Create**.)
+
+- **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
+- **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
+- **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
+    - Note the **Client ID**,**Client Secret**, and **slug** values because they will be required later.
+    - Add two `Strict` redirect URI and set them to <kbd>https://<em>freshrss.company</em>/i/oidc/</kbd> and <kbd>https://<em>freshrss.company:443</em>/i/oidc/</kbd>. If FreshRSS is exposed on a port other than `443`, update the second redirect URI accordingly.
+    - Select any available signing key.
+- **Configure Bindings** _(optional):_ you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user’s **My applications** page.
+
+## FreshRSS configuration
+
+:::info
+This integration is compatible only with Docker or Kubernetes installations of FreshRSS that use the [FreshRSS Docker image](https://hub.docker.com/r/freshrss/freshrss/) on x86_64 systems. Note that the Alpine version of the image is not supported. For more details, see [this issue on the FreshRSS GitHub repository](https://github.com/FreshRSS/FreshRSS/issues/5722).
+:::
+
+:::warning
+Before restarting your Docker container, ensure that at least one Admin user in your FreshRSS instance has a username that matches an authentik user.
+:::
+
+To enable OIDC login with FreshRSS, update your `.env` file to include the following variables:
+
+<IntegrationsMultilineCodeblock>
+    {`
+OIDC_ENABLED=1
+OIDC_PROVIDER_METADATA_URL=https://<em>authentik.company</em>/application/o/<em>your-application-slug</em>/.well-known/openid-configuration
+OIDC_CLIENT_ID=<em>Your Client ID from authentik</em>
+OIDC_CLIENT_SECRET=<em>Your Client Secret from authentik</em>
+OIDC_X_FORWARDED_HEADERS=X-Forwarded-Port X-Forwarded-Proto X-Forwarded-Host
+OIDC_SCOPES=openid email profile
+`}
+</IntegrationsMultilineCodeblock>
+
+Once your container or pod is restarted, attempt to login as a user that exists in both FreshRSS and authentik. Go to **Settings** -> **Authentication** and set the authentication method to **HTTP**.
+
+## References
+
+- [FreshRSS documentation for OpenID Connect](https://freshrss.github.io/FreshRSS/en/admins/16_OpenID-Connect.html).
+- [FreshRSS documentation for OIDC with authentik](https://freshrss.github.io/FreshRSS/en/admins/16_OpenID-Connect-Authentik.html)
+
+## Configuration verification
+
+To verify that authentik is correctly set up with FreshRSS, log out of FreshRSS and try logging back in using authentik. You should see a new button on the login page for OIDC authentication.

website/integrations/services/gatus/index.mdx

@@ -69,6 +69,10 @@ security:
 `}
 </IntegrationsMultilineCodeblock>
 
+## References
+
+- [Gatus Security documentation for OpenID Connect](https://github.com/TwiN/gatus?tab=readme-ov-file#oidc)
+
 ## Configuration verification
 
-To confirm that authentik is properly configured with Gatus, click the **Login with SSO** button found on the main page of your Gatus installation. A successful login will redirect you to your status page.
+To confirm that authentik is properly configured with Gatus, click the **Login with SSO** button found on the main page of your Gatus installation. A successful login should redirect you to your status page.