Skip to content

Commit 2519bce

Browse files
authored
website/integrations: move resource section to end of documents (#14668)
Moves the resource section to the end of each document Signed-off-by: Dewi Roberts <[email protected]>
1 parent 3e3615a commit 2519bce

File tree

18 files changed

+70
-70
lines changed

18 files changed

+70
-70
lines changed

website/integrations/services/actual-budget/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -102,10 +102,10 @@ The first user to log into Actual Budget via OpenID will become the owner and ad
102102
To do so, navigate to **Server online** > **User Directory**, and create users matching exiting authentik usernames. Then, grant access to the budget via the **User Access** tab.
103103
:::
104104

105-
## Resources
106-
107-
- [Official Actual Budget documentation on OpenID Connect integration](https://actualbudget.org/docs/experimental/oauth-auth/)
108-
109105
## Configuration verification
110106

111107
To confirm that authentik is properly configured with Actual Budget, visit your Actual Budget installation, select the OpenID login method from the dropdown menu, and click **Sign in with OpenID**.
108+
109+
## Resources
110+
111+
- [Official Actual Budget documentation on OpenID Connect integration](https://actualbudget.org/docs/experimental/oauth-auth/)

website/integrations/services/adventurelog/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -73,10 +73,10 @@ Ensure the `https://adventurelog.company/accounts` path is routed to the backend
7373

7474
Launch your authentik dashboard as an admin and find the AdventureLog app. Click **More details** then **Edit**. In the admin interface, click **Test** under **Check Access**. If you get a 403 error, you need to grant the user the correct permissions. This can be done by going to the user's profile and adding the correct permissions.
7575

76-
## Resources
77-
78-
- [AdventureLog's official documentation](https://adventurelog.app/docs/configuration/social_auth/authentik.html)
79-
8076
## Configuration verification
8177

8278
To confirm authentik is correctly integrated with AdventureLog, log out and attempt to log back in using OpenID Connect by clicking the **authentik** button on the AdventureLog login page.
79+
80+
## Resources
81+
82+
- [AdventureLog's official documentation](https://adventurelog.app/docs/configuration/social_auth/authentik.html)

website/integrations/services/apache-guacamole/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -188,10 +188,10 @@ This section depends on the operating system hosting Apache Guacamole.
188188
More information on the keytool command can be found in the [Oracle documentation.](https://docs.oracle.com/en/java/javase/21/docs/specs/man/keytool.html)
189189
:::
190190

191-
## Resources
192-
193-
- [Apache Guacamole official documentation on OpenID Connect integrations](https://guacamole.apache.org/doc/gug/openid-auth.html#configuring-guacamole-for-single-sign-on-with-openid-connect)
194-
195191
## Configuration verification
196192

197193
To verify that authentik is correctly configured with Apache Guacamole, log out and log back in through authentik. You should notice a new button appearing at the bottom left of the login page.
194+
195+
## Resources
196+
197+
- [Apache Guacamole official documentation on OpenID Connect integrations](https://guacamole.apache.org/doc/gug/openid-auth.html#configuring-guacamole-for-single-sign-on-with-openid-connect)

website/integrations/services/bookstack/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -122,12 +122,12 @@ Once that's done, the next step is to update your `.env` file to include the fol
122122
</TabItem>
123123
</Tabs>
124124

125+
## Configuration verification
126+
127+
To confirm that authentik is properly configured with BookStack, visit your BookStack installation, and click **Login with authentik**.
128+
125129
## Resources
126130

127131
- [BookStack Administrator Documentation for OpenID Connect](https://www.bookstackapp.com/docs/admin/oidc-auth/)
128132
- [Bookstack Administrator Documentation for SAML2](https://www.bookstackapp.com/docs/admin/saml2-auth/)
129133
- [PeerTube video detailing a setup with authentik (OpenID Connect)](https://foss.video/w/a744K8GxFF1LqBFSadAsuV)
130-
131-
## Configuration verification
132-
133-
To confirm that authentik is properly configured with BookStack, visit your BookStack installation, and click **Login with authentik**.

website/integrations/services/budibase/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -50,10 +50,10 @@ From the main page of your Budibase installation, add the following values under
5050
- **Callback URL**: <kbd>https://<em>budibase.company</em>/api/global/auth/oidc/callback/</kbd>
5151
- **Name**: <kbd>authentik</kbd>
5252

53-
## Resources
54-
55-
- [Budibase official documentation on OpenID Connect](https://docs.budibase.com/docs/openid-connect)
56-
5753
## Configuration verification
5854

5955
To confirm that authentik is properly configured with Budibase, visit your Budibase installation, and click **Sign in with authentik**.
56+
57+
## Resources
58+
59+
- [Budibase official documentation on OpenID Connect](https://docs.budibase.com/docs/openid-connect)

website/integrations/services/chronograf/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,10 @@ Refer to the [Chronograf configuration options documentation](https://docs.influ
6565
USE_ID_TOKEN=true
6666
```
6767

68-
## Resources
69-
70-
- [Chronograf official documentation on OpenID Connect integration](https://docs.influxdata.com/chronograf/v1/administration/managing-security/#configure-chronograf-to-use-any-oauth-20-provider)
71-
7268
## Configuration verification
7369

7470
To confirm that authentik is properly configured with Chronograf, visit your Chronograf installation, and click **Log in with authentik**.
71+
72+
## Resources
73+
74+
- [Chronograf official documentation on OpenID Connect integration](https://docs.influxdata.com/chronograf/v1/administration/managing-security/#configure-chronograf-to-use-any-oauth-20-provider)

website/integrations/services/cloudflare-access/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -55,10 +55,10 @@ To support the integration of Cloudflare Access with authentik, you need to crea
5555
4. Click **Save**.
5656
5. Click **Test** to verify the login provider.
5757

58-
## Resources
59-
60-
- [Cloudflare Access Generic OIDC documentation](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/generic-oidc/)
61-
6258
## Configuration verification
6359

6460
To confirm that authentik is properly configured with Cloudflare Access, click the **Test** button found right next-to the **Save** button from the previous step.
61+
62+
## Resources
63+
64+
- [Cloudflare Access Generic OIDC documentation](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/generic-oidc/)

website/integrations/services/coder/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,10 @@ CODER_OIDC_SIGN_IN_TEXT=Log in with authentik
5353
CODER_OIDC_ICON_URL=https://authentik.company/static/dist/assets/icons/icon.png
5454
```
5555

56-
## Resources
57-
58-
- [Coder OIDC authentication documentation](https://coder.com/docs/admin/users/oidc-auth/)
59-
6056
## Configuration verification
6157

6258
To confirm that authentik is properly configured with Coder, log out and attempt to log back in by clicking **Log in with authentik**.
59+
60+
## Resources
61+
62+
- [Coder OIDC authentication documentatiom](https://coder.com/docs/admin/users/oidc-auth/)

website/integrations/services/dokuwiki/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -75,11 +75,11 @@ For **oauthgeneric**:
7575

7676
Once that is done, navigate to the **Authentication** sub-section of the **Administration** interface's **Configuration Settings** section and enable **oauth** under **Authentication backend**.
7777

78+
## Configuration verification
79+
80+
To verify that authentik is correctly configured with DocuWiki, log out and log back in through authentik. You should notice a new button on the login page.
81+
7882
## Resources
7983

8084
- [DocuWiki OAuth plugin](https://www.dokuwiki.org/plugin:oauth)
8185
- [DocuWiki plugin for generic OAuth](https://www.dokuwiki.org/plugin:oauthgeneric)
82-
83-
## Configuration verification
84-
85-
To verify that authentik is correctly configured with DocuWiki, log out and log back in through authentik. You should notice a new button on the login page.

website/integrations/services/espocrm/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -61,10 +61,10 @@ Configure the following fields:
6161
- **JSON Web Key Set Endpoint**: <kbd>https://<em>authentik.company</em>/application/o/<em>your-application-slug</em>/jwks</kbd>
6262
- **Logout URL**: <kbd>https://<em>authentik.company</em>/application/o/<em>your-application-slug</em>/end_session</kbd>
6363

64-
## Resources
65-
66-
- [EspoCRM administrator documentation on OpenID Connect authentication](https://docs.espocrm.com/administration/oidc/)
67-
6864
## Configuration verification
6965

7066
To confirm that authentik is properly configured with EspoCRM, log out and log back in via authentik. Clicking the "Login" button on the homepage should redirect you to authentik.
67+
68+
## Resources
69+
70+
- [EspoCRM administrator documentation on OpenID Connect authentication](https://docs.espocrm.com/administration/oidc/)

website/integrations/services/firezone/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,11 +60,11 @@ Set the following values in the Firezone UI:
6060
- **Redirect URI**: <kbd>https://<em>firezone.company</em>/auth/oidc/authentik/callback/</kbd>
6161
- **Auth-create Users**: Turn this on
6262

63+
## Configuration verification
64+
65+
To verify that authentik is correctly set up with Firezone, navigate to your Firezone installation and click **authentik**. A successful login should redirect you to the main page of your installation.
66+
6367
## Resources
6468

6569
- [Firezone administration documentation on OpenID Connect authentication](https://www.firezone.dev/docs/authenticate/oidc/)
6670
- [Firezone OIDC troubleshooting documentation](https://www.firezone.dev/docs/administer/troubleshoot/#re-enable-local-authentication-via-cli)
67-
68-
## Configuration verification
69-
70-
To verify that authentik is correctly set up with Firezone, navigate to your Firezone installation and click **authentik**. A successful login should redirect you to the main page of your installation.

website/integrations/services/fortigate-admin/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -117,8 +117,8 @@ config system saml
117117
end
118118
```
119119

120+
## Configuration verification
121+
120122
## Resources
121123

122124
- [Offocial Fortigate documentation on SAML authentication](https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-SAML-SSO-login-for-FortiGate/ta-p/194656)
123-
124-
## Configuration verification

website/integrations/services/fortimanager/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,10 @@ To support the integration of FortiManager with authentik, you need to create an
5353
9. Set the **IdP Logout URL** to: <kbd>https://<em>authentik.company</em>/</kbd>
5454
10. In the **IdP Certificate** field, import your authentik certificate (either self-signed or valid).
5555

56-
## Resources
57-
58-
- [Community post on the Fortinet forum](https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-Configure-SAML-SSO-login-with-Azure-AD/ta-p/198324)
59-
6056
## Configuration verification
6157

6258
To confirm that authentik is properly configured with FortiManager, log out and log back in via authentik.
59+
60+
## Resources
61+
62+
- [Community post on the Fortinet forum](https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-Configure-SAML-SSO-login-with-Azure-AD/ta-p/198324)

website/integrations/services/frappe/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -90,10 +90,10 @@ To support the integration of Frappe with authentik, you need to create an appli
9090
4. **Save the Configuration**
9191
- Click the black **Save** button in the top-right corner to complete the setup.
9292

93-
## Resources
94-
95-
- [Frappe's official OpenID Connect guide](https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login)
96-
9793
## Configuration verification
9894

9995
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.
96+
97+
## Resources
98+
99+
- [Frappe's official OpenID Connect guide](https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login)

website/integrations/services/freshrss/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,11 @@ To enable OIDC login with FreshRSS, update your `.env` file to include the follo
6363

6464
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**.
6565

66+
## Configuration verification
67+
68+
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.
69+
6670
## Resources
6771

6872
- [FreshRSS documentation for OpenID Connect](https://freshrss.github.io/FreshRSS/en/admins/16_OpenID-Connect.html).
6973
- [FreshRSS documentation for OIDC with authentik](https://freshrss.github.io/FreshRSS/en/admins/16_OpenID-Connect-Authentik.html)
70-
71-
## Configuration verification
72-
73-
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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -63,10 +63,10 @@ Gatus automatically updates its configuration approximately every 30 seconds. If
6363
scopes: [openid]
6464
```
6565
66-
## Resources
67-
68-
- [Gatus Security documentation for OpenID Connect](https://github.com/TwiN/gatus?tab=readme-ov-file#oidc)
69-
7066
## Configuration verification
7167
7268
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.
69+
70+
## Resources
71+
72+
- [Gatus Security documentation for OpenID Connect](https://github.com/TwiN/gatus?tab=readme-ov-file#oidc)

website/integrations/services/gitea/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -193,10 +193,10 @@ gitea:
193193
scopes: "email profile"
194194
```
195195

196-
## Resources
197-
198-
- [Official Gitea Documentation](https://docs.gitea.com/)
199-
200196
## Configuration verification
201197

202198
To verify that authentik is correctly set up with Gitea, log out and then log back in using the **Sign in with authentik** button.
199+
200+
## Resources
201+
202+
- [Official Gitea Documentation](https://docs.gitea.com/)

website/integrations/services/youtrack/index.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -65,10 +65,10 @@ To support the integration of YouTrack with authentik, you need to create an app
6565
2. Navigate to **Applications** > **Providers** > **_application name_**, then click **Edit**.
6666
3. Replace the placeholder value for the **ACS URL** with the value copied from the previous section.
6767

68-
## Resources
69-
70-
- [YouTrack SAML 2.0 Auth Module Documentation](https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html)
71-
7268
## Configuration verification
7369

7470
To confirm that authentik is properly configured with YouTrack, log out and attempt to log back in. You should be redirected to authentik to complete authentication.
71+
72+
## Resources
73+
74+
- [YouTrack SAML 2.0 Auth Module Documentation](https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html)

0 commit comments

Comments
 (0)