website: fix incorrect usage of "login to" + "log into" vs "log in to" (#14772)
This commit is contained in:
@ -9,7 +9,7 @@ For detailed instructions, refer to Microsoft Entra ID documentation.
|
||||
|
||||
## Configure Entra ID
|
||||
|
||||
1. Log into the Azure portal and on the Home page, under Azure services, click on or search for **App registrations**.
|
||||
1. Log in to the Azure portal and on the Home page, under Azure services, click on or search for **App registrations**.
|
||||
2. On the **App registrations** page, click **New registration**.
|
||||
3. On the **Register an application** page, define the **Name** of the app, and under **Supported account types** select **Accounts in this organizational directory only**. Leave **Redirect URI** empty.
|
||||
4. Click **Register**.
|
||||
|
@ -13,7 +13,7 @@ The following placeholders are used in this guide:
|
||||
|
||||
## FreeIPA Setup
|
||||
|
||||
1. Log into FreeIPA.
|
||||
1. Log in to FreeIPA.
|
||||
|
||||
2. Create a user in FreeIPA, matching your naming scheme. Provide a strong password, example generation methods: `pwgen 64 1` or `openssl rand 36 | base64 -w 0`. After you are done click **Add and Edit**.
|
||||
|
||||
|
@ -26,7 +26,7 @@ To automate the deployment of this configuration use a [Group policy](https://su
|
||||
|
||||
## Windows / Internet Explorer
|
||||
|
||||
Log into the Windows machine using an account of your Kerberos realm (or administrative domain).
|
||||
Log in to the Windows machine using an account of your Kerberos realm (or administrative domain).
|
||||
|
||||
Open Internet Explorer, click **Tools** and then click **Internet Options**. You can also find **Internet Options** using the system search.
|
||||
|
||||
|
@ -21,7 +21,7 @@ The following placeholders are used in this guide:
|
||||
|
||||
## Apple
|
||||
|
||||
1. Log into your Apple developer account, and navigate to **Certificates, IDs & Profiles**, then click **Identifiers** in the sidebar.
|
||||
1. Log in to your Apple developer account, and navigate to **Certificates, IDs & Profiles**, then click **Identifiers** in the sidebar.
|
||||
2. Register a new Identifier with the type of **App IDs**, and the subtype **App**.
|
||||
3. Choose a name that users will recognise for the **Description** field.
|
||||
4. For your bundle ID, use the reverse domain of authentik, in this case `company.authentik`.
|
||||
|
@ -48,7 +48,7 @@ Finally, you need to publish the Facebook app.
|
||||
|
||||
## authentik configuration
|
||||
|
||||
1. Log into authentik as admin, and then navigate to **Directory -> Federation & Social login**
|
||||
1. Log in to authentik as admin, and then navigate to **Directory -> Federation & Social login**
|
||||
2. Click **Create**.
|
||||
3. In the **New Source** box, for **Select type** select **Facebook OAuth Source** and then click **Next**.
|
||||
4. Define the following fields:
|
||||
|
@ -14,7 +14,7 @@ The following placeholders are used in this guide:
|
||||
|
||||
## Mailcow
|
||||
|
||||
1. Log into mailcow as an admin and navigate to the OAuth2 Apps settings
|
||||
1. Log in to mailcow as an admin and navigate to the OAuth2 Apps settings
|
||||
|
||||

|
||||
|
||||
|
@ -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.
|
||||
|
@ -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.
|
||||
|
||||
|
@ -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.
|
||||
|
||||
|
@ -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:
|
||||
|
@ -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.
|
||||
|
||||
|
@ -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.
|
||||
|
||||
|
Reference in New Issue
Block a user