website/integrations-all: convert authentik configuration to wizard (#13144)

* init

* 6 more

* tana...

* quick reformat

* welp only time for one change

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* Revert "wip"

This reverts commit e71f0d22e3f093350e8d12eaad5e5c0f9d38253c.

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* wip

* a

website/integrations/services/freshrss/index.md

@@ -24,28 +24,22 @@ This documentation lists only the settings that you need to change from their de
 
 ## authentik configuration
 
-1. Create an **OAuth2/OpenID Provider** under **Applications** > **Providers** using the following settings:
+To support the integration of FreshRss with authentik, you need to create an application/provider pair in authentik.
 
-    - **Name**: FreshRSS
-    - **Authorization flow**: default-provider-authorization-explicit-consent
-    - **Protocol Settings**:
-        - **Client Type**: Confidential
-        - **Client ID**: Either create your own Client ID or use the auto-populated ID
-        - **Client Secret**: Either create your own Client Secret or use the auto-populated secret
-          :::note
-          Take note of the `Client ID` and `Client Secret`, you'll need them later.
-          :::
-    - **Redirect URIs/Origins**:
-        - `https://freshrss.company/i/oidc/`
-        - `https://freshrss.company:port/i/oidc`
-    - **Signing Key**: Any of your signing keys
-    - Leave everything else as default
+### Create an application and provider in authentik
 
-2. Create an **Application** under **Applications** > **Applications** using the following settings:
-    - **Name**: FreshRSS
-    - **Slug**: freshrss
-    - **Provider**: FreshRSS _(the provider you created in step 1)_
-    - Leave everything else as default
+1. Log in to authentik as an admin, and open the authentik Admin interface.
+2. Navigate to **Applications** > **Applications** and click **Create with Provider** 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.
+
+3. Click **Submit** to save the new application and provider.
 
 ## FreshRSS configuration