habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

website: fix incorrect usage of "login to" + "log into" vs "log in to" (#14772)

Browse Source
This commit is contained in:
Dominic R
2025-05-29 10:23:19 -04:00
committed by GitHub
parent 2519bcef89
commit 8f939fa577
12 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/integrations/services/atlassian/index.mdx
View File

@ -54,7 +54,7 @@ To support the integration of Atlassian Cloud with authentik, you need to create
### Download the signing certificate
1. Log into authentik as an admin, and open the authentik Admin interface.
1. Log in to authentik as an admin, and open the authentik Admin interface.
2. Navigate to **Applications** > **Providers** and click on the name of the newly created Atlassian Cloud provider.
3. Under **Download signing certificate** click the **Download** button. The contents of this certificate will be required in the next section.
@ -88,7 +88,7 @@ To support the integration of Atlassian Cloud with authentik, you need to create
### Internal users
1. Log into the [Atlassian administrator portal](https://admin.atlassian.com) as an Atlassian Cloud organization admin.
1. Log in to the [Atlassian administrator portal](https://admin.atlassian.com) as an Atlassian Cloud organization admin.
2. Navigate to **Security** > **Authentication policies**.
3. Click **Add policy** at the top right.
4. Select the `authentik` directory and provide a name for the policy.

2
website/integrations/services/harbor/index.md
View File

@ -49,7 +49,7 @@ To support the integration of Harbor with authentik, you need to create an appli
To support the integration of authentik with Harbor, you need to configure OIDC authentication.
1. Login to the Harbor dashboard as an admin.
1. Log in to the Harbor dashboard as an admin.
2. Navigate to **Configuration** and select the **Authentication** tab.
3. In the **Auth Mode** dropdown, select **OIDC** and provide the following required configurations.

4
website/integrations/services/netbird/index.md
View File

@ -57,7 +57,7 @@ If an access group is created for the Netbird application, the Netbird service a
### Set up a service account
1. Log into authentik as an admin, and open the authentik Admin interface.
1. Log in to authentik as an admin, and open the authentik Admin interface.
2. Navigate to **Directory** > **Users**, and click **Create a service account**.
3. Set the **Username** to `NetBird` and disable the **Create group** option. Click **Create** and take note of the **password**.
@ -65,7 +65,7 @@ If an access group is created for the Netbird application, the Netbird service a
NetBird requires the service account to have full administrative access to the authentik instance. Follow these steps to make it an administrator.
1. Log into authentik as an admin, and open the authentik Admin interface.
1. Log in to authentik as an admin, and open the authentik Admin interface.
2. Navigate to **Directory** > **Groups**, and click **`authentik Admins`**.
3. On the top of the group configuration page, switch to the **Users** tab near the top of the page, then click **Add existing user**, and select the service account you just created.

2
website/integrations/services/openproject/index.md
View File

@ -76,7 +76,7 @@ OpenProject requires a first and last name for each user. By default authentik o
To support the integration of authentik with OpenProject, you need to configure authentication in the OpenProject administration interface.
1. Login to OpenProject as an admin, click on your profile icon at the top right and then **Administration**.
1. Log in to OpenProject as an admin, click on your profile icon at the top right and then **Administration**.
2. Navigate to **Authentication** > **OpenID providers**.
3. Provide a display name (e.g. `Authentik`) and click **Save**.
4. Click on **I have a discover endpoint URL** and enter:

2
website/integrations/services/push-security/index.mdx
View File

@ -80,7 +80,7 @@ Push Security requires separate first and last names for each user, but authenti
### Download the signing certificate
1. Log into authentik as an administrator, and open the authentik Admin interface.
1. Log in to authentik as an administrator, and open the authentik Admin interface.
2. Navigate to **Applications** > **Providers** and click on the name of the newly created Push Security provider.
3. Click **Download** under **Download signing certificate**. The contents of this certificate will be required in the next section.

2
website/integrations/services/veeam-enterprise-manager/index.md
View File

@ -25,7 +25,7 @@ You will need an existing group or multiple in authentik to assign roles in Veea
## Veeam Enterprise Manager pre-configuration
Login to your Veeam Enterprise Manager. Navigate to the Configuration in the top-right. On the left sidebar, select Settings. Select the SAML Authentication tab.
Log in to your Veeam Enterprise Manager. Navigate to the Configuration in the top-right. On the left sidebar, select Settings. Select the SAML Authentication tab.
Check the checkbox called "Enable SAML 2.0". Further down the site, click the "Download" button, to download the metadata.