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 <dewi@goauthentik.io>
This commit is contained in:
@ -102,10 +102,10 @@ The first user to log into Actual Budget via OpenID will become the owner and ad
|
||||
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.
|
||||
:::
|
||||
|
||||
## Resources
|
||||
|
||||
- [Official Actual Budget documentation on OpenID Connect integration](https://actualbudget.org/docs/experimental/oauth-auth/)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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**.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Official Actual Budget documentation on OpenID Connect integration](https://actualbudget.org/docs/experimental/oauth-auth/)
|
||||
|
@ -73,10 +73,10 @@ Ensure the `https://adventurelog.company/accounts` path is routed to the backend
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [AdventureLog's official documentation](https://adventurelog.app/docs/configuration/social_auth/authentik.html)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [AdventureLog's official documentation](https://adventurelog.app/docs/configuration/social_auth/authentik.html)
|
||||
|
@ -188,10 +188,10 @@ This section depends on the operating system hosting Apache Guacamole.
|
||||
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)
|
||||
:::
|
||||
|
||||
## Resources
|
||||
|
||||
- [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)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [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)
|
||||
|
@ -122,12 +122,12 @@ Once that's done, the next step is to update your `.env` file to include the fol
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To confirm that authentik is properly configured with BookStack, visit your BookStack installation, and click **Login with authentik**.
|
||||
|
||||
## Resources
|
||||
|
||||
- [BookStack Administrator Documentation for OpenID Connect](https://www.bookstackapp.com/docs/admin/oidc-auth/)
|
||||
- [Bookstack Administrator Documentation for SAML2](https://www.bookstackapp.com/docs/admin/saml2-auth/)
|
||||
- [PeerTube video detailing a setup with authentik (OpenID Connect)](https://foss.video/w/a744K8GxFF1LqBFSadAsuV)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To confirm that authentik is properly configured with BookStack, visit your BookStack installation, and click **Login with authentik**.
|
||||
|
@ -50,10 +50,10 @@ From the main page of your Budibase installation, add the following values under
|
||||
- **Callback URL**: <kbd>https://<em>budibase.company</em>/api/global/auth/oidc/callback/</kbd>
|
||||
- **Name**: <kbd>authentik</kbd>
|
||||
|
||||
## Resources
|
||||
|
||||
- [Budibase official documentation on OpenID Connect](https://docs.budibase.com/docs/openid-connect)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To confirm that authentik is properly configured with Budibase, visit your Budibase installation, and click **Sign in with authentik**.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Budibase official documentation on OpenID Connect](https://docs.budibase.com/docs/openid-connect)
|
||||
|
@ -65,10 +65,10 @@ Refer to the [Chronograf configuration options documentation](https://docs.influ
|
||||
USE_ID_TOKEN=true
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [Chronograf official documentation on OpenID Connect integration](https://docs.influxdata.com/chronograf/v1/administration/managing-security/#configure-chronograf-to-use-any-oauth-20-provider)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To confirm that authentik is properly configured with Chronograf, visit your Chronograf installation, and click **Log in with authentik**.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Chronograf official documentation on OpenID Connect integration](https://docs.influxdata.com/chronograf/v1/administration/managing-security/#configure-chronograf-to-use-any-oauth-20-provider)
|
||||
|
@ -55,10 +55,10 @@ To support the integration of Cloudflare Access with authentik, you need to crea
|
||||
4. Click **Save**.
|
||||
5. Click **Test** to verify the login provider.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Cloudflare Access Generic OIDC documentation](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/generic-oidc/)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Cloudflare Access Generic OIDC documentation](https://developers.cloudflare.com/cloudflare-one/identity/idp-integration/generic-oidc/)
|
||||
|
@ -53,10 +53,10 @@ CODER_OIDC_SIGN_IN_TEXT=Log in with authentik
|
||||
CODER_OIDC_ICON_URL=https://authentik.company/static/dist/assets/icons/icon.png
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [Coder OIDC authentication documentation](https://coder.com/docs/admin/users/oidc-auth/)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To confirm that authentik is properly configured with Coder, log out and attempt to log back in by clicking **Log in with authentik**.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Coder OIDC authentication documentatiom](https://coder.com/docs/admin/users/oidc-auth/)
|
||||
|
@ -75,11 +75,11 @@ For **oauthgeneric**:
|
||||
|
||||
Once that is done, navigate to the **Authentication** sub-section of the **Administration** interface's **Configuration Settings** section and enable **oauth** under **Authentication backend**.
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [DocuWiki OAuth plugin](https://www.dokuwiki.org/plugin:oauth)
|
||||
- [DocuWiki plugin for generic OAuth](https://www.dokuwiki.org/plugin:oauthgeneric)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
@ -61,10 +61,10 @@ Configure the following fields:
|
||||
- **JSON Web Key Set Endpoint**: <kbd>https://<em>authentik.company</em>/application/o/<em>your-application-slug</em>/jwks</kbd>
|
||||
- **Logout URL**: <kbd>https://<em>authentik.company</em>/application/o/<em>your-application-slug</em>/end_session</kbd>
|
||||
|
||||
## Resources
|
||||
|
||||
- [EspoCRM administrator documentation on OpenID Connect authentication](https://docs.espocrm.com/administration/oidc/)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [EspoCRM administrator documentation on OpenID Connect authentication](https://docs.espocrm.com/administration/oidc/)
|
||||
|
@ -60,11 +60,11 @@ Set the following values in the Firezone UI:
|
||||
- **Redirect URI**: <kbd>https://<em>firezone.company</em>/auth/oidc/authentik/callback/</kbd>
|
||||
- **Auth-create Users**: Turn this on
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Firezone administration documentation on OpenID Connect authentication](https://www.firezone.dev/docs/authenticate/oidc/)
|
||||
- [Firezone OIDC troubleshooting documentation](https://www.firezone.dev/docs/administer/troubleshoot/#re-enable-local-authentication-via-cli)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
@ -117,8 +117,8 @@ config system saml
|
||||
end
|
||||
```
|
||||
|
||||
## Configuration verification
|
||||
|
||||
## Resources
|
||||
|
||||
- [Offocial Fortigate documentation on SAML authentication](https://community.fortinet.com/t5/FortiGate/Technical-Tip-Configuring-SAML-SSO-login-for-FortiGate/ta-p/194656)
|
||||
|
||||
## Configuration verification
|
||||
|
@ -53,10 +53,10 @@ To support the integration of FortiManager with authentik, you need to create an
|
||||
9. Set the **IdP Logout URL** to: <kbd>https://<em>authentik.company</em>/</kbd>
|
||||
10. In the **IdP Certificate** field, import your authentik certificate (either self-signed or valid).
|
||||
|
||||
## Resources
|
||||
|
||||
- [Community post on the Fortinet forum](https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-Configure-SAML-SSO-login-with-Azure-AD/ta-p/198324)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To confirm that authentik is properly configured with FortiManager, log out and log back in via authentik.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Community post on the Fortinet forum](https://community.fortinet.com/t5/FortiAnalyzer/Technical-Tip-Configure-SAML-SSO-login-with-Azure-AD/ta-p/198324)
|
||||
|
@ -90,10 +90,10 @@ To support the integration of Frappe with authentik, you need to create an appli
|
||||
4. **Save the Configuration**
|
||||
- Click the black **Save** button in the top-right corner to complete the setup.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Frappe's official OpenID Connect guide](https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Frappe's official OpenID Connect guide](https://docs.frappe.io/framework/user/en/guides/integration/openid_connect_and_frappe_social_login)
|
||||
|
@ -63,11 +63,11 @@ To enable OIDC login with FreshRSS, update your `.env` file to include the follo
|
||||
|
||||
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**.
|
||||
|
||||
## 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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [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.
|
||||
|
@ -63,10 +63,10 @@ Gatus automatically updates its configuration approximately every 30 seconds. If
|
||||
scopes: [openid]
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [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 should redirect you to your status page.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Gatus Security documentation for OpenID Connect](https://github.com/TwiN/gatus?tab=readme-ov-file#oidc)
|
||||
|
@ -193,10 +193,10 @@ gitea:
|
||||
scopes: "email profile"
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [Official Gitea Documentation](https://docs.gitea.com/)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
To verify that authentik is correctly set up with Gitea, log out and then log back in using the **Sign in with authentik** button.
|
||||
|
||||
## Resources
|
||||
|
||||
- [Official Gitea Documentation](https://docs.gitea.com/)
|
||||
|
@ -65,10 +65,10 @@ To support the integration of YouTrack with authentik, you need to create an app
|
||||
2. Navigate to **Applications** > **Providers** > **_application name_**, then click **Edit**.
|
||||
3. Replace the placeholder value for the **ACS URL** with the value copied from the previous section.
|
||||
|
||||
## Resources
|
||||
|
||||
- [YouTrack SAML 2.0 Auth Module Documentation](https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html)
|
||||
|
||||
## Configuration verification
|
||||
|
||||
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.
|
||||
|
||||
## Resources
|
||||
|
||||
- [YouTrack SAML 2.0 Auth Module Documentation](https://www.jetbrains.com/help/youtrack/server/saml-authentication-module.html)
|
||||
|
Reference in New Issue
Block a user