diff --git a/website/docs/add-secure-apps/applications/manage_apps.mdx b/website/docs/add-secure-apps/applications/manage_apps.mdx index 6c5e0a90bd..cdaa807252 100644 --- a/website/docs/add-secure-apps/applications/manage_apps.mdx +++ b/website/docs/add-secure-apps/applications/manage_apps.mdx @@ -10,7 +10,7 @@ To add an application to authentik and have it display on users' **My applicatio 1. Log in to authentik as an administrator 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.)** +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. Alternatively, you can first create a provider separately, then create the application and connect it to the provider. 3. In the **New application** box, define the application details, the provider type and configuration settings, and bindings for the application. - **Application**: provide a name, an optional group for the type of application, the policy engine mode, and optional UI settings. @@ -96,10 +96,10 @@ return { 1. Open the Admin interface and navigate to **Applications > Applications**. 2. Click the name of the application for which you want to create an entitlement. -3. Click the **Application entitlements** tab at the top of the page, and then click **Create entitlement**. Provide a name for the entitlement, enter any optional **Attributes**, and then click **Create**. +3. Click the **Application entitlements** tab at the top of the page, and then click **New Entitlement**. Provide a name for the entitlement, enter any optional **Attributes**, and then click **Create**. 4. In the list locate the entitlement to which you want to bind a user or group, and then **click the caret (>) to expand the entitlement details.** 5. In the expanded area, click **Bind existing Group/User**. -6. In the **Create Binding** box, select either the tab for **Group** or **User**, and then in the drop-down list, select the group or user. +6. In the **New Binding** box, select either the tab for **Group** or **User**, and then in the drop-down list, select the group or user. 7. Optionally, configure additional settings for the binding, and then click **Create** to create the binding and close the box. ## Hide applications diff --git a/website/docs/add-secure-apps/flows-stages/stages/authenticator_email/index.md b/website/docs/add-secure-apps/flows-stages/stages/authenticator_email/index.md index 72676f412b..75aa78dfa7 100644 --- a/website/docs/add-secure-apps/flows-stages/stages/authenticator_email/index.md +++ b/website/docs/add-secure-apps/flows-stages/stages/authenticator_email/index.md @@ -14,7 +14,7 @@ The email address will be saved and can be used with the [Authenticator validati To use the Email Authenticator Setup stage in a flow, follow these steps: 1. [Create](../../flow/index.md#create-a-flow) a new flow or edit an existing one. -2. On the flow's **Stage Bindings** tab, click **Create and bind stage** to create and add the Email Authenticator Setup stage. (If the stage already exists, click **Bind existing stage**.) +2. On the flow's **Stage Bindings** tab, click **New Stage** to create and add the Email Authenticator Setup stage. (If the stage already exists, click **Bind Existing Stage**.) 3. Configure the stage settings as described below. - **Name**: provide a descriptive name, such as Email Authenticator Setup. - **Authenticator type name**: define the display name for this stage. diff --git a/website/docs/add-secure-apps/flows-stages/stages/captcha/index.md b/website/docs/add-secure-apps/flows-stages/stages/captcha/index.md index 991ebd1b97..8bf4099c5e 100644 --- a/website/docs/add-secure-apps/flows-stages/stages/captcha/index.md +++ b/website/docs/add-secure-apps/flows-stages/stages/captcha/index.md @@ -48,7 +48,7 @@ See https://developers.cloudflare.com/turnstile/get-started/migrating-from-recap #### Configuration options 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages** > **Stages** and click **Create**. +2. Navigate to **Flows and Stages** > **Stages** and click **New Stage**. 3. Select **Captcha Stage** and click **Next**. 4. Provide a descriptive name for the stage (e.g. `authentication-captcha`) and configure the following required settings based on the values of your [Cloudflare Turnstile Widget](https://developers.cloudflare.com/turnstile/concepts/widget/): - Under **Stage-specific settings**: diff --git a/website/docs/add-secure-apps/flows-stages/stages/index.md b/website/docs/add-secure-apps/flows-stages/stages/index.md index 082d2d39f7..540b42b29d 100644 --- a/website/docs/add-secure-apps/flows-stages/stages/index.md +++ b/website/docs/add-secure-apps/flows-stages/stages/index.md @@ -41,7 +41,7 @@ To create a stage, follow these steps: 1. Log in as an admin to authentik, and go to the Admin interface. 2. In the Admin interface, navigate to **Flows and Stages > Stages**. -3. Click **Create**, define the stage using the configuration settings, and then click **Finish**. +3. Click **New Stage**, select the stage type, define the stage using the configuration settings, and then click **Create Stage**. After creating the stage, you can then use bindings to determine whether or not the stage will be implemented in the flow. @@ -65,7 +65,7 @@ To bind a stage to a flow (which adds the stage as a "step" in the flow), follow 2. In the Admin interface, navigate to **Flows and Stages > Flows**. 3. In the list of flows, click the name of the flow to which you want to bind one or more stages. 4. On the Flow page, click the **Stage Bindings** tab at the top. -5. Here, you can decide if you want to create a new stage and bind it to the flow (**Create and bind Stage**), or if you want to select an existing stage and bind it to the flow (**Bind existing stage**). +5. Here, you can decide if you want to create a new stage and bind it to the flow (**New Stage**), or if you want to select an existing stage and bind it to the flow (**Bind Existing Stage**). ### Control access to a stage @@ -88,6 +88,6 @@ To bind a user or a group to a stage binding for a specific flow, follow these s 6. In the expanded area, click **Bind existing policy/group/user**. 7. In the **Create Binding** box, select either the tab for **Group** or **User**. 8. In the drop-down list, select the group or user. -9. Optionally, configure additional settings for the binding, and then click **Create** to create the binding and close the box. +9. Optionally, configure additional settings for the binding, and then click **Create Stage Binding** to create the binding and close the box. Learn more about the different types of [bindings](../../bindings-overview/index.md) in authentik and [working with them](../../bindings-overview/work-with-bindings.md). diff --git a/website/docs/add-secure-apps/flows-stages/stages/mtls/index.md b/website/docs/add-secure-apps/flows-stages/stages/mtls/index.md index a20375cc23..b74fdb39c7 100644 --- a/website/docs/add-secure-apps/flows-stages/stages/mtls/index.md +++ b/website/docs/add-secure-apps/flows-stages/stages/mtls/index.md @@ -105,7 +105,7 @@ When using authentik without a reverse proxy, select the certificate authorities 2. Navigate to **System** > **Certificates**, and either generate or add the certificate you’ll use as a certificate authority. -3. Then, navigate to **Flows and Stages** > **Stages** and click **Create**. Select **Mutual TLS Stage**, click **Next**, and set the following fields: +3. Then, navigate to **Flows and Stages** > **Stages** and click **New Stage**. Select **Mutual TLS Stage**, click **Next**, and set the following fields: - **Name**: provide a descriptive name, such as "chrome-device-trust". - **Stage-specific settings**: diff --git a/website/docs/add-secure-apps/flows-stages/stages/password/index.md b/website/docs/add-secure-apps/flows-stages/stages/password/index.md index ac17166484..ed76a09473 100644 --- a/website/docs/add-secure-apps/flows-stages/stages/password/index.md +++ b/website/docs/add-secure-apps/flows-stages/stages/password/index.md @@ -7,7 +7,7 @@ This is a generic password prompt that authenticates the current `pending_user`. ## Create a Password stage 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages > Stages** and click **Create**. +2. Navigate to **Flows and Stages > Stages** and click **New Stage**. 3. In the **New Stage** dialog select **Password stage**, and then click **Next**. 4. Provide the following settings: diff --git a/website/docs/add-secure-apps/providers/entra/create-entra-provider.md b/website/docs/add-secure-apps/providers/entra/create-entra-provider.md index f6b471ec19..216abb5b0c 100644 --- a/website/docs/add-secure-apps/providers/entra/create-entra-provider.md +++ b/website/docs/add-secure-apps/providers/entra/create-entra-provider.md @@ -12,9 +12,9 @@ To create an Entra ID provider in authentik, you must have already [configured E ## Create an Entra ID provider in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers** and click **Create**. +2. Navigate to **Applications** > **Providers** and click **New Provider**. 3. Select **Microsoft Entra Provider** as the provider type, then click **Next**. -4. On the **Create Microsoft Entra Provider** page, set the following configurations: +4. On the **New Microsoft Entra Provider** page, set the following configurations: - **Name**: provide a descriptive name (e.g. `Entra ID provider`) - Under **Protocol settings**: - **Client ID**: the Client ID that you copied when [configuring Entra ID](./configure-entra.md) @@ -38,7 +38,7 @@ To create an Entra ID provider in authentik, you must have already [configured E ## Create an Entra ID application in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications**, click **Create**, and set the following configurations: +2. Navigate to **Applications** > **Applications**, click **New Application**, and set the following configurations: - **Name**: provide a name for the application (e.g. `Entra ID`) - **Slug**: enter the name that you want to appear in the URL - **Provider**: this field should be left empty @@ -62,7 +62,7 @@ These are limited access accounts that must use email for verification when logg This is possible via a modified property mapping: 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Customization** > **Property Mappings** and click **Create**. +2. Navigate to **Customization** > **Property Mappings** and click **New Property Mapping**. 3. Select **Microsoft Entra Provider Mapping** as the property mapping type and click **Next**. 4. Provide a **Name** for the property mapping and set the following **Expression**: diff --git a/website/docs/add-secure-apps/providers/gws/create-gws-provider.md b/website/docs/add-secure-apps/providers/gws/create-gws-provider.md index 37cb11e3d6..5feb32b0b6 100644 --- a/website/docs/add-secure-apps/providers/gws/create-gws-provider.md +++ b/website/docs/add-secure-apps/providers/gws/create-gws-provider.md @@ -12,9 +12,9 @@ To create a Google Workspace provider in authentik, you must have already [confi ## Create a Google Workspace provider in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers** and click **Create**. +2. Navigate to **Applications** > **Providers** and click **New Provider**. 3. Select **Google Workspace Provider** as the provider type, then click **Next**. -4. On the **Create Google Workspace Provider** page, set the following configurations: +4. On the **New Google Workspace Provider** page, set the following configurations: - **Name**: provide a descriptive name (e.g. `GWS provider`) - Under **Protocol settings**: - **Credentials**: paste the contents of the JSON file that you downloaded when [configuring Google Workspace](./configure-gws.md) @@ -42,7 +42,7 @@ If you have configured the [Google Workspace SAML integration](/integrations/ser ::: 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications**, click **Create**, and set the following configurations: +2. Navigate to **Applications** > **Applications**, click **New Application**, and set the following configurations: - **Name**: provide a name for the application (e.g. `GWS`) - **Slug**: enter the name that you want to appear in the URL - **Provider**: when _not_ used in conjunction with the [Google SAML configuration](/integrations/cloud-providers/google), this should be left empty. diff --git a/website/docs/add-secure-apps/providers/index.mdx b/website/docs/add-secure-apps/providers/index.mdx index a8d1ca5896..9169fdf620 100644 --- a/website/docs/add-secure-apps/providers/index.mdx +++ b/website/docs/add-secure-apps/providers/index.mdx @@ -9,7 +9,7 @@ A Provider is an authentication method, a service that is used by authentik to a Providers are the "other half" of [applications](../applications/index.md). They typically exist in a 1-to-1 relationship; each application needs a provider and every provider can be used with one application. -You can create a new provider in the Admin interface, or you can use the [**Create with Provider** option](../applications/manage_apps.mdx#create-an-application-and-provider-pair) to create a new application and its provider at the same time. +You can create a new provider in the Admin interface, or you can use the [**New Application** option](../applications/manage_apps.mdx#create-an-application-and-provider-pair) to create a new application and its provider at the same time. Applications can use additional providers to augment the functionality of the main provider. For more information, see [Backchannel providers](../applications/manage_apps.mdx#backchannel-providers). diff --git a/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx b/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx index 625a6343a2..a162d58a93 100644 --- a/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx +++ b/website/docs/add-secure-apps/providers/ldap/create-ldap-provider.mdx @@ -61,7 +61,7 @@ Finally, you'll need to create a User Login Stage. Now you'll need to create the LDAP authentication flow and bind the previously created stages. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages** > **Flows**, click **Create**, and set the following required configurations: +2. Navigate to **Flows and Stages** > **Flows**, click **New Flow**, and set the following required configurations: - Provide a **Name**, **Title** and **Slug** for the flow (e.g. `ldap-authentication-flow`). - Set **Designation** to `Authentication`. 3. Click **Create**. @@ -75,7 +75,7 @@ Now you'll need to create the LDAP authentication flow and bind the previously c The LDAP application and provider can now be created. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications**, click **Create with Provider** to create an application and provider pair. +2. Navigate to **Applications** > **Applications**, click **New Application** to create an application and provider pair. 3. On the **New application** page, define the application details, and then click **Next**. 4. Select **LDAP Provider** as the **Provider Type**, and then click **Next**. 5. On the **Configure LDAP Provider** page, provide the configuration settings and then click **Submit** to create both the application and the provider. @@ -117,7 +117,7 @@ The service account needs permissions to search the LDAP directory. You'll need The LDAP provider requires the deployment of an LDAP [Outpost](../../outposts/index.mdx). 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Outposts**, click **Create** and set the following required configurations: +2. Navigate to **Applications** > **Outposts**, click **New Outpost** and set the following required configurations: - Provide a **Name** for the outpost (e.g. `LDAP Outpost'). - Set the **Type** as `LDAP`. - Set **Integration** to match your deployment method or manually deploy an outpost via [Docker-Compose](../../outposts/manual-deploy-docker-compose.md) or [Kubernetes](../../outposts/manual-deploy-kubernetes.md). For more information, refer to the [Outpost documentation](../../outposts/index.mdx). diff --git a/website/docs/add-secure-apps/providers/oauth2/create-oauth2-provider.md b/website/docs/add-secure-apps/providers/oauth2/create-oauth2-provider.md index 89ab33c7bf..cec8a29201 100644 --- a/website/docs/add-secure-apps/providers/oauth2/create-oauth2-provider.md +++ b/website/docs/add-secure-apps/providers/oauth2/create-oauth2-provider.md @@ -2,10 +2,10 @@ title: Create an OAuth2 provider --- -To create a provider along with the corresponding application that uses it for authentication, navigate to **Applications** > **Applications** and click **Create with provider**. We recommend this combined approach for most common use cases. Alternatively, you can use the legacy method to solely create the provider by navigating to **Applications** > **Providers** and clicking **Create**. +To create a provider along with the corresponding application that uses it for authentication, navigate to **Applications** > **Applications** and click **New Provider**. We recommend this combined approach for most common use cases. Alternatively, you can use the legacy method to solely create the provider by navigating to **Applications** > **Providers** and clicking **Create**. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications > Applications** and click **Create with provider** to create an application and provider pair. +2. Navigate to **Applications > Applications** and click **New Provider** to create an application and provider pair. 3. On the **New application** page, define the application settings, and then click **Next**. 4. Select **OAuth2/OIDC** as the **Provider Type**, and then click **Next**. 5. On the **Configure OAuth2/OpenId Provider** page, provide the configuration settings and then click **Submit** to create both the application and the provider. diff --git a/website/docs/add-secure-apps/providers/oauth2/device_code.md b/website/docs/add-secure-apps/providers/oauth2/device_code.md index 6359d39a9f..2ed0ab2dbc 100644 --- a/website/docs/add-secure-apps/providers/oauth2/device_code.md +++ b/website/docs/add-secure-apps/providers/oauth2/device_code.md @@ -64,7 +64,7 @@ If the user _has_ finished the authentication and authorization, the response wi ### Create and apply a device code flow 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages** > **Flows** and click **Create**. +2. Navigate to **Flows and Stages** > **Flows** and click **New Flow**. 3. Set the following required configurations: - **Name**: provide a name (e.g. `default-device-code-flow`) - **Title**: provide a title (e.g. `Device code flow`) diff --git a/website/docs/add-secure-apps/providers/rac/create-rac-provider.md b/website/docs/add-secure-apps/providers/rac/create-rac-provider.md index 0d421ae2b2..682307dd07 100644 --- a/website/docs/add-secure-apps/providers/rac/create-rac-provider.md +++ b/website/docs/add-secure-apps/providers/rac/create-rac-provider.md @@ -21,10 +21,10 @@ Depending on whether you are connecting using RDP, SSH, or VNC, the exact config ### Create a RAC provider and application pair -To create a provider along with the corresponding application that uses it for authentication, navigate to **Applications** > **Applications** and click **Create with Provider**. We recommend this combined approach for most common use cases. Alternatively, you can use the legacy method to create only the provider by navigating to **Applications** > **Providers** and clicking **Create**. +To create a provider along with the corresponding application that uses it for authentication, navigate to **Applications** > **Applications** and click **New Application**. We recommend this combined approach for most common use cases. Alternatively, you can use the legacy method to create only the provider by navigating to **Applications** > **Providers** and clicking **New Provider**. 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications** and click **Create with Provider** to create an application and provider pair. +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. 3. On the **New application** page, define the application details, and then click **Next**. 4. Select the **RAC** provider type, and then click **Next**. 5. On the **Configure Remote Access Provider** page, provide the configuration settings and then click **Submit** to create both the application and the provider. @@ -36,9 +36,9 @@ Next, you need to add property mappings for each remote machine you want to acce Refer to the [RAC Credentials Prompt](./rac_credentials_prompt.md) and [RAC SSH Public Key Authentication](./rac-public-key.md) documentation for alternative methods of handling RAC authentication. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Customization** > **Property Mappings**, and click **Create**. +2. Navigate to **Customization** > **Property Mappings**, and click **New Property Mapping**. 3. Select **RAC Provider Property Mapping** as the property mapping type, and then click **Next**. -4. On the **Create RAC Provider Property Mapping** page, provide the following configuration settings: +4. On the **New RAC Provider Property Mapping** page, provide the following configuration settings: - **Name**: provide a name for the property mapping - Under **General settings**: - **Username**: the username for the remote machine @@ -55,7 +55,7 @@ Then, you need to create an endpoint corresponding to each remote machine you wa 1. Log in to authentik as an administrator and open the authentik Admin interface. 2. Navigate to **Applications** > **Providers**. 3. Click the **Edit** button on the RAC provider that you previously created. -4. On the Provider page, under **Endpoints**, click **Create**, and provide the following settings: +4. On the Provider page, under **Endpoints**, click **New RAC Endpoint**, and provide the following settings: - **Provider Name** (endpoint name): define a name for the endpoint - **Protocol**: select the appropriate protocol - **Host**: enter the host name or IP address of the remote machine. Optionally include the port. diff --git a/website/docs/add-secure-apps/providers/rac/rac-public-key.md b/website/docs/add-secure-apps/providers/rac/rac-public-key.md index 7094bf8435..9979170051 100644 --- a/website/docs/add-secure-apps/providers/rac/rac-public-key.md +++ b/website/docs/add-secure-apps/providers/rac/rac-public-key.md @@ -60,7 +60,7 @@ The pipe character (`|`) is required to preserve linebreaks in the YAML text. Se ## Apply a private key to an RAC property mapping 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Customization** > **Property Mappings** and click **Create**, then create a **RAC Provider Property Mapping** with the following settings: +2. Navigate to **Customization** > **Property Mappings** and click **New Property Mapping**, then create a **RAC Provider Property Mapping** with the following settings: - **Name**: Choose a descriptive name - Under **Advanced Settings**: - **Expression**: @@ -95,7 +95,7 @@ The pipe character (`|`) is required to preserve linebreaks in the YAML text. Se ## Retrieve a private key from a user's attributes and apply it to an RAC property mapping 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Customization** > **Property Mappings** and click **Create**. Create a **RAC Provider Property Mapping** with the following settings: +2. Navigate to **Customization** > **Property Mappings** and click **New Property Mapping**. Create a **RAC Provider Property Mapping** with the following settings: - **Name**: Choose a descriptive name - Under **Advanced Settings**: - **Expression**: diff --git a/website/docs/add-secure-apps/providers/rac/rac_credentials_prompt.md b/website/docs/add-secure-apps/providers/rac/rac_credentials_prompt.md index dfa170e723..8da3a2fbfa 100644 --- a/website/docs/add-secure-apps/providers/rac/rac_credentials_prompt.md +++ b/website/docs/add-secure-apps/providers/rac/rac_credentials_prompt.md @@ -18,7 +18,7 @@ This configurations requires: ## Create a new authorization flow 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages** > **Flows**, click **Create**, and enter the following required settings: +2. Navigate to **Flows and Stages** > **Flows**, click **New Flow**, and enter the following required settings: - **Name**: Enter a descriptive name for the flow. - **Title**: Enter a title for the flow. This will be displayed to users when they're prompted for their credentials. - **Slug**: Enter a slug for the flow. This will be displayed in the flow URL. @@ -29,15 +29,15 @@ This configurations requires: ## Create prompts 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages** > **Prompts**, click **Create**, and enter the following required settings: +2. Navigate to **Flows and Stages** > **Prompts**, click **New Prompt**, and enter the following required settings: - **Name**: Enter a descriptive name for the prompt (e.g. `username`). - **Field Key**: `connection_settings.username` - **Label**: Enter a label for the field which will be displayed above it. - **Type**: `Text` - **Required**: Toggled on. - **Order**: `0` -3. Click **Create** to save the prompt. -4. On the **Prompts** page, click **Create** again, and enter the following required settings: +3. Click **Create Prompt** to save the prompt. +4. On the **Prompts** page, click **New Prompt** again, and enter the following required settings: - **Name**: Enter a descriptive name for the prompt (e.g. `password`). - **Field Key**: `connection_settings.password` - **Label**: Enter a label for the field which will be displayed above it. @@ -55,7 +55,7 @@ You can optionally add other prompt fields such as `domain` (e.g. `connection_se 1. Log in to authentik as an administrator and open the authentik Admin interface. 2. Navigate to **Flows and Stages** > **Flows**. 3. Click the name of the newly created authorization flow. -4. Click on **Stage bindings**, click **Create and bind stage**, and enter the following required settings: +4. Click on **Stage bindings**, click **New Stage**, and enter the following required settings: - **Select Type**: Select `Prompt stage` as the prompt type. - **Create Prompt Stage**: - **Name**: Enter a name for the prompt stage. diff --git a/website/docs/add-secure-apps/providers/saml/create-saml-provider.md b/website/docs/add-secure-apps/providers/saml/create-saml-provider.md index 933ef630ec..3206d43c23 100644 --- a/website/docs/add-secure-apps/providers/saml/create-saml-provider.md +++ b/website/docs/add-secure-apps/providers/saml/create-saml-provider.md @@ -6,10 +6,10 @@ authentik SAML providers can be created either from scratch or by using SAML met ## Create a SAML provider and application pair -To create a provider along with the corresponding application that uses it for authentication, navigate to **Applications** > **Applications** and click **Create with provider**. We recommend this combined approach for most common use cases. Alternatively, you can use the legacy method to solely create the provider by navigating to **Applications** > **Providers** and clicking **Create**. +To create a provider along with the corresponding application that uses it for authentication, navigate to **Applications** > **Applications** and click **New Provider**. We recommend this combined approach for most common use cases. Alternatively, you can use the legacy method to solely create the provider by navigating to **Applications** > **Providers** and clicking **Create**. 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications** and click **Create with provider** to create an application and provider pair. +2. Navigate to **Applications** > **Applications** and click **New Provider** to create an application and provider pair. 3. On the **New application** page, define the application details, and then click **Next**. 4. Select **SAML Provider** as the **Provider Type**, and then click **Next**. 5. On the **Configure SAML Provider** page, provide the configuration settings and then click **Submit** to create both the application and the provider. @@ -19,9 +19,9 @@ To create a provider along with the corresponding application that uses it for a If you have exported SAML metadata from your SP, you can optionally create the authentik SAML provider by importing this metadata. 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers** and click **Create** to create a provider. +2. Navigate to **Applications** > **Providers** and click **New Provider** to create a provider. 3. Select **SAML Provider from Metadata** as the **Provider Type**, and then click **Next**. -4. On the **Create SAML Provider from Metadata** page, provide the configuration settings along with an SP metadata file and then click **Finish** to create the provider. +4. On the **New SAML Provider from Metadata** page, provide the configuration settings along with an SP metadata file and then click **Finish** to create the provider. 5. (Optional) Edit the created SAML provider and configure any further settings. ## Export authentik SAML provider metadata @@ -33,7 +33,7 @@ After an authentik SAML provider has been created via any of the above methods, To download the metadata of an authentik SAML provider, follow these steps: 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers**. +2. Navigate to **Applications** > **Providers**. 3. Click the name of the provider you want metadata from to open its overview tab. 4. In the **Related objects** section, under **Metadata** click on **Download**. This will download the metadata XML file for that provider. @@ -42,7 +42,7 @@ To download the metadata of an authentik SAML provider, follow these steps: To view and optionally download the metadata of an authentik SAML provider, follow these steps: 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers**. +2. Navigate to **Applications** > **Providers**. 3. Click the name of the provider you want metadata from to open its overview tab. 4. Navigate to the **Metadata** tab. 5. The metadata for the provider will be shown in a codebox. You can optionally use the **Download** button to obtain the metadata as a file. diff --git a/website/docs/add-secure-apps/providers/ssf/create-ssf-provider.md b/website/docs/add-secure-apps/providers/ssf/create-ssf-provider.md index bc1dee78ee..d648559477 100644 --- a/website/docs/add-secure-apps/providers/ssf/create-ssf-provider.md +++ b/website/docs/add-secure-apps/providers/ssf/create-ssf-provider.md @@ -16,22 +16,22 @@ Follow this workflow to create and configure an SSF provider for an application: ## Create the SSF provider 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers** and click **Create** to create a provider. +2. Navigate to **Applications** > **Providers** and click **New Provider** to create a provider. 3. Select **Shared Signals Framework Provider** as the **Provider Type**, and then click **Next**. -4. On the **Create SSF Provider** page, provide the configuration settings. Be sure to select a **Signing Key**. +4. On the **New SSF Provider** page, provide the configuration settings. Be sure to select a **Signing Key**. 5. Click **Finish** to create the provider. ## Create the OIDC provider 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Providers** and click **Create** to create a provider. +2. Navigate to **Applications** > **Providers** and click **New Provider** to create a provider. 3. Select **OAuth2/OpenID Provider** as the **Provider Type**, and then click **Next**. -4. On the **Create OAuth2/OpenID Provider** page, provide the configuration settings and then click **Finish** to create the provider. +4. On the **New OAuth2/OpenID Provider** page, provide the configuration settings and then click **Finish** to create the provider. ## Create the application 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications** and click **Create** to create an application. +2. Navigate to **Applications** > **Applications** and click **New Application** to create an application. 3. Configure the following required settings for the application: - **Name**: provide a descriptive name of the application. - **Slug**: provide the application slug used in URLs. diff --git a/website/docs/add-secure-apps/providers/wsfed/create-wsfed-provider.md b/website/docs/add-secure-apps/providers/wsfed/create-wsfed-provider.md index 1abbc1a670..30e459d3da 100644 --- a/website/docs/add-secure-apps/providers/wsfed/create-wsfed-provider.md +++ b/website/docs/add-secure-apps/providers/wsfed/create-wsfed-provider.md @@ -7,7 +7,7 @@ An authentik WS-Federation provider is typically created as part of an applicati ## Create a WS-Federation provider and application pair 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications > Applications** and click **Create with provider** to create an application and provider pair. +2. Navigate to **Applications > Applications** and click **New Provider** to create an application and provider pair. 3. On the **New application** page, define the application details, and then click **Next**. 4. Select **WS-Federation Provider** as the **Provider Type**, and then click **Next**. 5. On the **Configure WS-Federation Provider** page, provide a name for the provider, select an authorization flow, and the two required configuration settings: @@ -24,7 +24,7 @@ After an authentik WS-Federation provider has been created via any of the above To download the metadata of an authentik WS-Federation provider, follow these steps: 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications > Providers**. +2. Navigate to **Applications > Providers**. 3. Click the name of the provider you want metadata for. 4. On the **Overview** tab, in the **Related objects** section, click on **Download** under **Metadata**. This will download the metadata XML file for that provider. @@ -33,6 +33,6 @@ To download the metadata of an authentik WS-Federation provider, follow these st To view and optionally download the metadata of an authentik WS-Federation provider, follow these steps: 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Applications > Providers**. +2. Navigate to **Applications > Providers**. 3. Click the name of the provider you want metadata for, and then click the **Metadata** tab. 4. The metadata for the provider will be shown in a code box. You can optionally use the **Download** button to obtain the metadata as a file. diff --git a/website/docs/customize/blueprints/v1/models.mdx b/website/docs/customize/blueprints/v1/models.mdx index 30ea59d3a2..b78b034294 100644 --- a/website/docs/customize/blueprints/v1/models.mdx +++ b/website/docs/customize/blueprints/v1/models.mdx @@ -30,7 +30,7 @@ For example: Via the standard API, a user's password can only be set via the separate `/api/v3/core/users//set_password/` endpoint. In blueprints, the password of a user can be set using the `password` field. -Keep in mind that if an LDAP Source is configured and the user maps to an LDAP user, this password change will be propagated to the LDAP server. +Keep in mind that if an LDAP Source is configured and the user maps to an LDAP user, this password change will be propagated to the LDAP server. For example: diff --git a/website/docs/customize/file-picker.md b/website/docs/customize/file-picker.md index ba92fa8347..58dc030c37 100644 --- a/website/docs/customize/file-picker.md +++ b/website/docs/customize/file-picker.md @@ -12,7 +12,7 @@ This applies to: - **System** > **Brands** > **Default flow background** - **Flows and Stages** > **Flows** > **Background** - **Applications** > **Applications** > **Icon** -- **Applications** > **Create application** wizard > **Icon** +- **Applications** > **New Application** wizard > **Icon** - **Directory** > **Federation and Social login** > source **Icon** fields for SAML, OAuth, Plex, and Kerberos sources ## Accepted values diff --git a/website/docs/developer-docs/contributing.md b/website/docs/developer-docs/contributing.md index 70c53d7a18..83fbe448ad 100644 --- a/website/docs/developer-docs/contributing.md +++ b/website/docs/developer-docs/contributing.md @@ -49,47 +49,47 @@ authentik ├── lib - Generic library of functions, few dependencies on other packages. ├── outposts - Configure and deploy outposts on Kubernetes and Docker. ├── policies - General PolicyEngine -│   ├── dummy - A Dummy policy used for testing -│   ├── event_matcher - Match events based on different criteria -│   ├── expiry - Check when a user's password was last set -│   ├── expression - Execute any arbitrary python code -│   ├── password - Check a password against several rules -│   └── reputation - Check the user's/client's reputation +│ ├── dummy - A Dummy policy used for testing +│ ├── event_matcher - Match events based on different criteria +│ ├── expiry - Check when a user's password was last set +│ ├── expression - Execute any arbitrary python code +│ ├── password - Check a password against several rules +│ └── reputation - Check the user's/client's reputation ├── providers -│   ├── ldap - Provide LDAP access to authentik users/groups using an outpost -│   ├── oauth2 - OIDC-compliant OAuth2 provider -│   ├── proxy - Provides an identity-aware proxy using an outpost -│   ├── radius - Provides a RADIUS server that authenticates using flows -│   ├── saml - SAML2 provider -│   └── scim - SCIM provider +│ ├── ldap - Provide LDAP access to authentik users/groups using an outpost +│ ├── oauth2 - OIDC-compliant OAuth2 provider +│ ├── proxy - Provides an identity-aware proxy using an outpost +│ ├── radius - Provides a RADIUS server that authenticates using flows +│ ├── saml - SAML2 provider +│ └── scim - SCIM provider ├── recovery - Generate keys to use in case you lock yourself out ├── root - Root Django application, contains global settings and routes ├── sources -│   ├── kerberos - Sync Kerberos users into authentik -│   ├── ldap - Sync LDAP users from OpenLDAP or Active Directory into authentik -│   ├── oauth - OAuth1 and OAuth2 source -│   ├── plex - Plex source -│   ├── saml - SAML2 source -│   └── telegram - Telegram source +│ ├── kerberos - Sync Kerberos users into authentik +│ ├── ldap - Sync LDAP users from OpenLDAP or Active Directory into authentik +│ ├── oauth - OAuth1 and OAuth2 source +│ ├── plex - Plex source +│ ├── saml - SAML2 source +│ └── telegram - Telegram source ├── stages -│   ├── authenticator_duo - Configure a DUO authenticator -│   ├── authenticator_static - Configure TOTP backup keys -│   ├── authenticator_totp - Configure a TOTP authenticator -│   ├── authenticator_validate - Validate any authenticator -│   ├── authenticator_webauthn - Configure a WebAuthn / Passkeys authenticator -│   ├── captcha - Make the user pass a captcha -│   ├── consent - Let the user decide if they want to consent to an action -│   ├── deny - Static deny, can be used with policies -│   ├── dummy - Dummy stage to test -│   ├── email - Send the user an email and block execution until they click the link -│   ├── identification - Identify a user with any combination of fields -│   ├── invitation - Invitation system to limit flows to certain users -│   ├── password - Password authentication -│   ├── prompt - Arbitrary prompts -│   ├── user_delete - Delete the currently pending user -│   ├── user_login - Login the currently pending user -│   ├── user_logout - Logout the currently pending user -│   └── user_write - Write any currently pending data to the user. +│ ├── authenticator_duo - Configure a DUO authenticator +│ ├── authenticator_static - Configure TOTP backup keys +│ ├── authenticator_totp - Configure a TOTP authenticator +│ ├── authenticator_validate - Validate any authenticator +│ ├── authenticator_webauthn - Configure a WebAuthn / Passkeys authenticator +│ ├── captcha - Make the user pass a captcha +│ ├── consent - Let the user decide if they want to consent to an action +│ ├── deny - Static deny, can be used with policies +│ ├── dummy - Dummy stage to test +│ ├── email - Send the user an email and block execution until they click the link +│ ├── identification - Identify a user with any combination of fields +│ ├── invitation - Invitation system to limit flows to certain users +│ ├── password - Password authentication +│ ├── prompt - Arbitrary prompts +│ ├── user_delete - Delete the currently pending user +│ ├── user_login - Login the currently pending user +│ ├── user_logout - Logout the currently pending user +│ └── user_write - Write any currently pending data to the user. ├── tasks - Background tasks └── tenants - Soft tenancy, configure defaults and branding per domain ``` diff --git a/website/docs/endpoint-devices/authentik-agent/agent-deployment/automated.mdx b/website/docs/endpoint-devices/authentik-agent/agent-deployment/automated.mdx index 7250b3d55f..c2fc64cbff 100644 --- a/website/docs/endpoint-devices/authentik-agent/agent-deployment/automated.mdx +++ b/website/docs/endpoint-devices/authentik-agent/agent-deployment/automated.mdx @@ -18,7 +18,7 @@ If you have already created an enrollment token, skip to the next section. 1. Log in to authentik as an administrator and open the authentik Admin interface. 2. Navigate to **Endpoint Devices** > **Connectors**. 3. Click on the authentik Agent connector that you created when [configuring your authentik deployment](../configuration.md) to support the authentik Agent. -4. Under **Enrollment Tokens**, click **Create**, and configure the following settings: +4. Under **Enrollment Tokens**, click **New Enrollment Token**, and configure the following settings: - **Token name**: provide a descriptive name for the token - **Device group _(optional)_**: select a device access group for the device to be added to after completing enrollment - **Expiring _(optional)_**: set whether or not the enrollment token will expire diff --git a/website/docs/endpoint-devices/authentik-agent/agent-deployment/linux.mdx b/website/docs/endpoint-devices/authentik-agent/agent-deployment/linux.mdx index 2887bfaff7..f63f30d0dd 100644 --- a/website/docs/endpoint-devices/authentik-agent/agent-deployment/linux.mdx +++ b/website/docs/endpoint-devices/authentik-agent/agent-deployment/linux.mdx @@ -25,7 +25,7 @@ If you have already created have an enrollment token, skip to the [next section] 1. Log in to authentik as an administrator and open the authentik Admin interface. 2. Navigate to **Endpoint Devices** > **Connectors**. 3. Click on the authentik Agent connector that you created when [configuring your authentik deployment](../configuration.md) to support the authentik agent. -4. Under **Enrollment Tokens**, click **Create**, and configure the following settings: +4. Under **Enrollment Tokens**, click **New Enrollment Token**, and configure the following settings: - **Token name**: provide a descriptive name for the token - **Device group _(optional)_**: select a device access group for the device to be added to after completing enrollment - **Expiring _(optional)_**: set whether or not the enrollment token will expire diff --git a/website/docs/endpoint-devices/authentik-agent/agent-deployment/macos.md b/website/docs/endpoint-devices/authentik-agent/agent-deployment/macos.md index adca9a8599..c0df870413 100644 --- a/website/docs/endpoint-devices/authentik-agent/agent-deployment/macos.md +++ b/website/docs/endpoint-devices/authentik-agent/agent-deployment/macos.md @@ -22,7 +22,7 @@ If you already have an enrollment token, skip to the [next section](#install-the 1. Log in to authentik as an administrator and open the authentik Admin interface. 2. Navigate to **Endpoint Devices** > **Connectors**. 3. Click on the authentik Agent connector that you created when [configuring your authentik deployment](../configuration.md) to support the authentik agent. -4. Under **Enrollment Tokens**, click **Create**, and configure the following settings: +4. Under **Enrollment Tokens**, click **New Enrollment Token**, and configure the following settings: - **Token name**: provide a descriptive name for the token - **Device group _(optional)_**: select a device access group for the device to be added to after completing enrollment - **Expiring _(optional)_**: set whether or not the enrollment token will expire diff --git a/website/docs/endpoint-devices/authentik-agent/agent-deployment/windows.md b/website/docs/endpoint-devices/authentik-agent/agent-deployment/windows.md index 7888cc317f..58820dc6a3 100644 --- a/website/docs/endpoint-devices/authentik-agent/agent-deployment/windows.md +++ b/website/docs/endpoint-devices/authentik-agent/agent-deployment/windows.md @@ -41,7 +41,7 @@ If you already have an enrollment token, skip to the [next section](#install-the 1. Log in to authentik as an administrator and open the authentik Admin interface. 2. Navigate to **Endpoint Devices** > **Connectors**. 3. Click on the authentik Agent connector that you created when [configuring your authentik deployment](../configuration.md) to support the authentik agent. -4. Under **Enrollment Tokens**, click **Create**, and configure the following settings: +4. Under **Enrollment Tokens**, click **New Enrollment Token**, and configure the following settings: - **Token name**: provide a descriptive name for the token - **Device group _(optional)_**: select a device access group for the device to be added to after completing enrollment - **Expiring _(optional)_**: set whether or not the enrollment token will expire diff --git a/website/docs/endpoint-devices/authentik-agent/configuration.md b/website/docs/endpoint-devices/authentik-agent/configuration.md index 5965df026e..de01d52f8b 100644 --- a/website/docs/endpoint-devices/authentik-agent/configuration.md +++ b/website/docs/endpoint-devices/authentik-agent/configuration.md @@ -18,7 +18,7 @@ The OAuth device code flow enables secure authentication for input-limited clien If you have already deployed the authentik OAuth device code flow, skip to the [next section](#create-an-application-and-provider-in-authentik-for-cli). 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages** > **Flows** and click **Create**. +2. Navigate to **Flows and Stages** > **Flows** and click **New Flow**. 3. Set the following required configurations: - **Name**: provide a name (e.g. `default-device-code-flow`) - **Title**: provide a title (e.g. `Device code flow`) @@ -34,7 +34,7 @@ If you have already deployed the authentik OAuth device code flow, skip to the [ The authentik Agent requires an OAuth application/provider pair to handle authentication. 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it to the provider. +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. Alternatively, you can first create a provider separately, then create the application and connect it to the provider. - **Application**: set the **Name** and **Slug** to `authentik-cli`, and provide 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. @@ -52,7 +52,7 @@ The authentik Agent requires an OAuth application/provider pair to handle authen The authentik Agent [Connector](../device-compliance/connectors/authentik-agent.md) allows device information to be reported to authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Endpoint Devices** > **Connectors** and click **Create**. +2. Navigate to **Endpoint Devices** > **Connectors** and click **New Endpoint Connector**. 3. Select **Agent Connector** as the agent type and click **Next**. 4. Configure the following required settings: - **Connector name**: provide a descriptive name (e.g. `authentik Agent`) diff --git a/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/aws.mdx b/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/aws.mdx index c5343b479d..9ee4edb264 100644 --- a/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/aws.mdx +++ b/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/aws.mdx @@ -18,7 +18,7 @@ To support the integration of authentik Agent with AWS CLI, you need to create a ### Create an application and provider in authentik for AWS CLI 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.) - **Application**: provide a descriptive name (e.g. `authentik-aws-cli`), 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. diff --git a/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/k8s.mdx b/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/k8s.mdx index f859041948..42e65c0b17 100644 --- a/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/k8s.mdx +++ b/website/docs/endpoint-devices/authentik-agent/device-authentication/cli-app-authentication/k8s.mdx @@ -18,7 +18,7 @@ To support the integration of authentik Agent with `kubectl`, you need to create ### Create an application and provider in authentik for Kubernetes 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.) - **Application**: provide a descriptive name (e.g. `kubernetes-cluster`), 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. diff --git a/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/linux.md b/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/linux.md index e550442405..0f2fd92fed 100644 --- a/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/linux.md +++ b/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/linux.md @@ -32,8 +32,8 @@ When configured correctly, when logging in you should see a prompt for **authent Local device login requires that the authenticating user is authorized to access the device. Access is controlled via [device access groups](../device-access-groups.mdx), which always apply. On Enterprise, direct device bindings (users, groups, or policies bound directly to the device) also affect access. If no device access group or direct binding is configured with the appropriate bindings, **all login attempts will be denied**. -1. In the Admin interface, navigate to **Endpoint Devices** > **Device access groups** and click **Create**. -2. Provide a **Group name** (e.g. `linux-devices`) and click **Create**. +1. In the Admin interface, navigate to **Endpoint Devices** > **Device access groups** and click **New Device Access Group**. +2. Provide a **Group name** (e.g. `linux-devices`) and click **Create Device Access Group**. 3. Expand the newly created device access group and click **Bind existing Policy / Group / User**. 4. Select **Group** and choose a group that contains the users who should be allowed to log in to the device. Alternatively, bind a specific **User** or a **Policy**. 5. Click **Create**. diff --git a/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/windows.md b/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/windows.md index 4b65706077..668d1aebfa 100644 --- a/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/windows.md +++ b/website/docs/endpoint-devices/authentik-agent/device-authentication/local-device-login/windows.md @@ -46,8 +46,8 @@ Currently, only local login is supported; RDP login is not yet available and is Local device login requires that the authenticating user is authorized to access the device. Access is controlled via [device access groups](../device-access-groups.mdx), which always apply. On Enterprise, direct device bindings (users, groups, or policies bound directly to the device) also affect access. If no device access group or direct binding is configured with the appropriate bindings, **all login attempts will be denied**. -1. In the Admin interface, navigate to **Endpoint Devices** > **Device access groups** and click **Create**. -2. Provide a **Group name** (e.g. `windows-devices`) and click **Create**. +1. In the Admin interface, navigate to **Endpoint Devices** > **Device access groups** and click **New Device Access Group**. +2. Provide a **Group name** (e.g. `windows-devices`) and click **Create Device Access Group**. 3. Expand the newly created device access group and click **Bind existing Policy / Group / User**. 4. Select **Group** and choose a group that contains the users who should be allowed to log in to the device. Alternatively, bind a specific **User** or a **Policy**. 5. Click **Create**. diff --git a/website/docs/endpoint-devices/device-compliance/connectors/authentik-agent.md b/website/docs/endpoint-devices/device-compliance/connectors/authentik-agent.md index 647cfecd52..58172eea3d 100644 --- a/website/docs/endpoint-devices/device-compliance/connectors/authentik-agent.md +++ b/website/docs/endpoint-devices/device-compliance/connectors/authentik-agent.md @@ -16,7 +16,7 @@ The agent connector mainly holds configuration for the agent itself, as well as Follow these instructions to configure the authentik Agent connector: 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Endpoint Devices** > **Connectors** and click **Create**. +2. Navigate to **Endpoint Devices** > **Connectors** and click **New Endpoint Connector**. 3. Select **Agent Connector** as the connector type, click **Next**, and configure the following required settings: - **Connector name**: provide a descriptive name for the connector. - **Refresh interval**: select how often the agent will attempt to update its configuration. diff --git a/website/docs/endpoint-devices/device-compliance/connectors/fleetdm.md b/website/docs/endpoint-devices/device-compliance/connectors/fleetdm.md index f5485e5a0c..506370abb3 100644 --- a/website/docs/endpoint-devices/device-compliance/connectors/fleetdm.md +++ b/website/docs/endpoint-devices/device-compliance/connectors/fleetdm.md @@ -24,7 +24,7 @@ Do not use an API key from a normal user because these keys expire. Follow these instructions to configure the Fleet connector in authentik: 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Endpoint Devices** > **Connectors** and click **Create**. +2. Navigate to **Endpoint Devices** > **Connectors** and click **New Endpoint Connector**. 3. Select **Fleet Connector** as the connector type, click **Next**, and configure the following settings: - **Connector name**: provide a descriptive name for the connector. - **Fleet Server URL**: enter your **Fleet web address** URL. diff --git a/website/docs/endpoint-devices/device-compliance/connectors/google-chrome.md b/website/docs/endpoint-devices/device-compliance/connectors/google-chrome.md index 63c14d92a2..7d29299912 100644 --- a/website/docs/endpoint-devices/device-compliance/connectors/google-chrome.md +++ b/website/docs/endpoint-devices/device-compliance/connectors/google-chrome.md @@ -65,7 +65,7 @@ For detailed instructions, refer to Google documentation. ### Create the connector 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Endpoint Devices** > **Connectors** and click **Create**. +2. Navigate to **Endpoint Devices** > **Connectors** and click **New Endpoint Connector**. 3. Select **Google Device Trust Connector** as the connector type, click **Next**, and configure the following settings: - **Name**: define a descriptive name, such as "chrome-device-trust". - **Google Verified Access API** diff --git a/website/docs/endpoint-devices/device-compliance/device-compliance-policy.md b/website/docs/endpoint-devices/device-compliance/device-compliance-policy.md index ac82672464..401e317f1e 100644 --- a/website/docs/endpoint-devices/device-compliance/device-compliance-policy.md +++ b/website/docs/endpoint-devices/device-compliance/device-compliance-policy.md @@ -39,9 +39,9 @@ If your goal is to only allow authentication via endpoint devices, this is achie #### Create an Endpoint stage 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages > Flows**. +2. Navigate to **Flows and Stages > Flows**. 3. Select the authentication flow that you want to modify. -4. Open the **Stage Bindings** tab and click **Create and bind stage**. +4. Open the **Stage Bindings** tab and click **New Stage**. 5. Select Endpoint stage as the stage type, click **Next**, and configure the following settings: - **Name**: provide a name for the stage - **Connector**: select a connector for the stage to fetch device facts from (e.g. `authentik agent`) @@ -59,9 +59,9 @@ The following example will only allow authentication via Apple devices. #### Create an Endpoint stage 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Flows and Stages > Flows**. +2. Navigate to **Flows and Stages > Flows**. 3. Select the authentication flow that you want to modify. -4. Open the **Stage Bindings** tab and click **Create and bind stage**. +4. Open the **Stage Bindings** tab and click **New Stage**. 5. Select Endpoint stage as the stage type, click **Next**, and configure the following settings: - **Name**: provide a name for the stage - **Connector**: select a connector for the stage to fetch device facts from (e.g. `authentik agent`) @@ -72,7 +72,7 @@ The following example will only allow authentication via Apple devices. #### Create a Deny stage -9. On the **Stage Bindings** tab, click **Create and bind stage**. +9. On the **Stage Bindings** tab, click **New Stage**. 10. Select **Deny Stage** as the stage type and configure the following settings: - **Name**: provide a name for the stage - **Deny message**: provide a message explaining why access was denied diff --git a/website/docs/install-config/install/aws.md b/website/docs/install-config/install/aws.md index c348c34ebd..a68311cef9 100644 --- a/website/docs/install-config/install/aws.md +++ b/website/docs/install-config/install/aws.md @@ -17,7 +17,7 @@ Under the **Certificate ARN** input, enter the previously created certificate AR This stack will create the following resources: -- AWS SSM secrets for the PostgreSQL user and the authentik secret key +- AWS SSM secrets for the PostgreSQL user and the authentik secret key - A VPC for all other resources - A RDS PostgreSQL Multi-AZ cluster - An ECS cluster with two tasks: diff --git a/website/docs/releases/old/v0.14.md b/website/docs/releases/old/v0.14.md index 99ac4df6b4..7e1ddcd456 100644 --- a/website/docs/releases/old/v0.14.md +++ b/website/docs/releases/old/v0.14.md @@ -50,7 +50,7 @@ This release does not introduce any new requirements. ### docker-compose -Download the docker-compose file for 0.14 from  [here](https://goauthentik.io/version/0.14/docker-compose.yml). Afterwards, simply run `docker-compose up -d` and then the standard upgrade command of `docker-compose run --rm server migrate`. +Download the docker-compose file for 0.14 from [here](https://goauthentik.io/version/0.14/docker-compose.yml). Afterwards, simply run `docker-compose up -d` and then the standard upgrade command of `docker-compose run --rm server migrate`. ### Kubernetes diff --git a/website/docs/security/audits-and-certs/2024-11-cobalt.md b/website/docs/security/audits-and-certs/2024-11-cobalt.md index c2b7889cad..798a804628 100644 --- a/website/docs/security/audits-and-certs/2024-11-cobalt.md +++ b/website/docs/security/audits-and-certs/2024-11-cobalt.md @@ -2,7 +2,7 @@ We are committed to engaging in regular pentesting and security audits of authentik. Defining and adhering to a cadence of external testing ensures a stronger probability that our code base, our features, and our architecture is as secure and non-exploitable as possible. -In August-September of 2024, we had a pentest conducted by [Cobalt](https://www.cobalt.io). This document covers the findings of the audit, how we addressed the noted issues, and the subsequent [re-testing](https://goauthentik.io/resources/fullReport_authentik-cobalt-test-instance-august-2024-pt26135.pdf) by Cobalt to confirm that all issues were resolved. +In August-September of 2024, we had a pentest conducted by [Cobalt](https://www.cobalt.io). This document covers the findings of the audit, how we addressed the noted issues, and the subsequent [re-testing](https://goauthentik.io/resources/fullReport_authentik-cobalt-test-instance-august-2024-pt26135.pdf) by Cobalt to confirm that all issues were resolved. Cobalt described their process for testing: @@ -18,7 +18,7 @@ In total, there were 5 low-level and one info-level vulnerabilities reported. By ## Responses to specific findings -From the audit, this is the complete list of findings, with information about how we addressed each. +From the audit, this is the complete list of findings, with information about how we addressed each. ### HTML Injection @@ -30,7 +30,7 @@ From the audit, this is the complete list of findings, with information about h **Issue**: The pentesters discovered that the application was susceptible to insecure file upload and stored Cross-Site Scripting (XSS) vulnerabilities by uploading crafted SVG files that were used as application icons. (This action could only be performed by an authenticated admin user, and thus had little practical value as an attack vector.) -**Fix**: The fix was to add a CSP header to files that are stored in the `/media` directory of the installation. For details, refer to [Pull Request #12092](https://github.com/goauthentik/authentik/pull/12092). +**Fix**: The fix was to add a CSP header to files that are stored in the `/media` directory of the installation. For details, refer to [Pull Request #12092](https://github.com/goauthentik/authentik/pull/12092). ### Vulnerability through footer links on website @@ -60,4 +60,4 @@ The absence of Content Security Policy (CSP) headers means that the application The subsequent retest conducted by Cobalt deemed all issues resolved. See page 17 of the [report](https://goauthentik.io/resources/fullReport_authentik-cobalt-test-instance-august-2024-pt26135.pdf) for the mitigation status ("fixed") for each of the issues discovered in September. -We are pleased to share this pentest and the final results of the retest. We encourage an open and ongoing communication with our users and community. For more information abut our security stance, read our [Security Policy](https://docs.goauthentik.io/docs/security/policy), [Hardening authentik](https://docs.goauthentik.io/docs/security/security-hardening), and our other [security-related documentation](https://docs.goauthentik.io/docs/security). If you have any questions or feedback you can reach us on [GitHub](https://github.com/goauthentik/authentik), [Discord](https://discord.com/channels/809154715984199690/809154716507963434), or via email to [hello@goauthentik.io](mailto:hello@goauthentik.io). +We are pleased to share this pentest and the final results of the retest. We encourage an open and ongoing communication with our users and community. For more information abut our security stance, read our [Security Policy](https://docs.goauthentik.io/docs/security/policy), [Hardening authentik](https://docs.goauthentik.io/docs/security/security-hardening), and our other [security-related documentation](https://docs.goauthentik.io/docs/security). If you have any questions or feedback you can reach us on [GitHub](https://github.com/goauthentik/authentik), [Discord](https://discord.com/channels/809154715984199690/809154716507963434), or via email to [hello@goauthentik.io](mailto:hello@goauthentik.io). diff --git a/website/docs/sys-mgmt/brands/index.md b/website/docs/sys-mgmt/brands/index.md index 8c5abf3b64..713f085c64 100644 --- a/website/docs/sys-mgmt/brands/index.md +++ b/website/docs/sys-mgmt/brands/index.md @@ -12,7 +12,7 @@ For an overview of branding and other customization options in authentik refer t To create or edit a brand, follow these steps: -1. Log in as an administrator, open the authentik Admin interface, and navigate to **System** > **Brands**. +1. Log in as an administrator, open the authentik Admin interface, and navigate to **System** > **Brands**. 2. Click **Create** to add a new brand, or click the **Edit** icon next to an existing brand to modify it. diff --git a/website/docs/sys-mgmt/events/notifications.md b/website/docs/sys-mgmt/events/notifications.md index 3aa2035574..9b813b5d7d 100644 --- a/website/docs/sys-mgmt/events/notifications.md +++ b/website/docs/sys-mgmt/events/notifications.md @@ -48,7 +48,7 @@ For more code examples, see [notification rule expression policies](./notificati After you've created the policies to match the events you want, create a notification rule. -1. Log in as an administrator, open the authentik Admin interface, and navigate to **Event > Notification Rules**. +1. Log in as an administrator, open the authentik Admin interface, and navigate to **Event > Notification Rules**. 2. Click **New Notification Rule** to add a new notification rule or click the **Edit** icon next to an existing rule to modify it. diff --git a/website/docs/sys-mgmt/events/transports.md b/website/docs/sys-mgmt/events/transports.md index 459bea48c2..67036928d6 100644 --- a/website/docs/sys-mgmt/events/transports.md +++ b/website/docs/sys-mgmt/events/transports.md @@ -77,8 +77,8 @@ This sends a request using the Slack-specific format. This is also compatible wi ## Create a notification transport -1. Log in as an administrator to the authentik Admin interface, and then navigate to **Event > Notification Transports**. +1. Log in as an administrator to the authentik Admin interface, and then navigate to **Event > Notification Transports**. -2. Click **Create** to add a new transport or click the **Edit** icon next to an existing notification transport to modify it. +2. Click **New Notification Transport** to add a new transport or click the **Edit** icon next to an existing notification transport to modify it. -3. Define the **Name** and **Mode** for the notification transport, enter required configuration settings, and then click **Create**. +3. Define the **Name** and **Mode** for the notification transport, enter required configuration settings, and then click **Create Notification Transport**. diff --git a/website/docs/users-sources/roles/manage_roles.md b/website/docs/users-sources/roles/manage_roles.md index f17fd5bbde..684ae11d91 100644 --- a/website/docs/users-sources/roles/manage_roles.md +++ b/website/docs/users-sources/roles/manage_roles.md @@ -14,7 +14,7 @@ Roles are intended to be assigned to groups, not to individual users. However, i To create a new role, follow these steps: 1. In the Admin interface, navigate to **Directory > Roles**. -2. Click **Create**, enter the name of the role, and then click **Create** in the box. +2. Click **New Role**, enter the name of the role, and then click **Create Role** to save. 3. Next, [assign permissions for the role](../access-control/manage_permissions.md#assign-or-remove-permissions-for-a-specific-role). ## Modify a role diff --git a/website/docs/users-sources/sources/directory-sync/freeipa/index.md b/website/docs/users-sources/sources/directory-sync/freeipa/index.md index efbf3bce74..41691ad0b4 100644 --- a/website/docs/users-sources/sources/directory-sync/freeipa/index.md +++ b/website/docs/users-sources/sources/directory-sync/freeipa/index.md @@ -53,7 +53,7 @@ See the [LDAP Source documentation](../../protocols/ldap) for more information o To create a new LDAP Source in authentik: 1. Log in to authentik as an administrator, and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social Login**, click **Create**, select **LDAP Source**, and click **Next**. +2. Navigate to **Directory** > **Federation and Social Login**, click **New Source**, select **LDAP Source**, and click **Next**. 3. Configure the following settings: - **Name**: Provide a descriptive name for the LDAP source. - **Slug**: Provide a slug for the LDAP source. diff --git a/website/docs/users-sources/sources/protocols/kerberos/index.md b/website/docs/users-sources/sources/protocols/kerberos/index.md index 1b1b948407..4aa9f20b9b 100644 --- a/website/docs/users-sources/sources/protocols/kerberos/index.md +++ b/website/docs/users-sources/sources/protocols/kerberos/index.md @@ -124,7 +124,7 @@ These property mappings are configured with the most common Kerberos setups. ### Expression data -The following variable is available to Kerberos source property mappings: +The following variable is available to Kerberos source property mappings: - `principal`: a Python string containing the Kerberos principal. For example `alice@REALM.COMPANY` or `HTTP/authentik.company@REALM.COMPANY`. diff --git a/website/docs/users-sources/sources/protocols/ldap/index.md b/website/docs/users-sources/sources/protocols/ldap/index.md index b70229dae4..e2ce60fc10 100644 --- a/website/docs/users-sources/sources/protocols/ldap/index.md +++ b/website/docs/users-sources/sources/protocols/ldap/index.md @@ -90,7 +90,7 @@ These are configured with most common LDAP setups. ### Expression data -The following variables are available to LDAP source property mappings: +The following variables are available to LDAP source property mappings: - `ldap`: A Python dictionary containing data from LDAP. - `dn`: The object DN. diff --git a/website/docs/users-sources/sources/protocols/oauth/index.mdx b/website/docs/users-sources/sources/protocols/oauth/index.mdx index 557cd07c05..4467aab218 100644 --- a/website/docs/users-sources/sources/protocols/oauth/index.mdx +++ b/website/docs/users-sources/sources/protocols/oauth/index.mdx @@ -39,7 +39,7 @@ See the [overview](../../property-mappings/index.md) for information on how prop ### Expression data -The following variables are available to OAuth source property mappings: +The following variables are available to OAuth source property mappings: - `info`: A Python dictionary containing OAuth claims. For example (values might differ depending on the source): ```python diff --git a/website/docs/users-sources/sources/protocols/saml/index.md b/website/docs/users-sources/sources/protocols/saml/index.md index d190ee65e9..4401f7d4f2 100644 --- a/website/docs/users-sources/sources/protocols/saml/index.md +++ b/website/docs/users-sources/sources/protocols/saml/index.md @@ -88,7 +88,7 @@ See the [overview](../../property-mappings/index.md) for information on how prop ### Expression data -The following variables are available to SAML source property mappings: +The following variables are available to SAML source property mappings: - `root`: An XML `ETree` object containing data from the source. - `name_id`: An XML `Element` object identifying the user. diff --git a/website/docs/users-sources/sources/social-logins/apple/index.md b/website/docs/users-sources/sources/social-logins/apple/index.md index a9179fa960..d34b1369e8 100644 --- a/website/docs/users-sources/sources/social-logins/apple/index.md +++ b/website/docs/users-sources/sources/social-logins/apple/index.md @@ -60,7 +60,7 @@ To integrate Apple with authentik, you will need to register two identifiers and To support the integration of Apple with authentik, you need to create an Apple OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, then configure the following settings: - **Select type**: select **Apple OAuth Source**. - **Create Apple OAuth Source**: provide a name, a slug which must match the slug used in the Apple `Return URL`, and the following required configurations: - Under **Protocol Settings**: diff --git a/website/docs/users-sources/sources/social-logins/discord/index.md b/website/docs/users-sources/sources/social-logins/discord/index.md index 91cbea2155..2412b296f7 100644 --- a/website/docs/users-sources/sources/social-logins/discord/index.md +++ b/website/docs/users-sources/sources/social-logins/discord/index.md @@ -28,7 +28,7 @@ To integrate Discord with authentik you will need to create an OAuth application ## authentik configuration 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Discord OAuth Source** as the source type. - **Create Discord OAuth Source**: provide a name, a slug which must match the slug used in the Discord `Redirect URI` (e.g. `discord`), and the following required configurations: - Under **Protocol Settings**: @@ -179,7 +179,7 @@ return user_matched 5. Click **Finish**. You can now bind this policy to the chosen enrollment and/or authentication flow of the Discord OAuth source. 6. Navigate to **Flows and Stages** > **Flows** and click the name of the flow in question. 7. Open the **Policy/Group/User Bindings** tab and click **Bind existing Policy/Group/User**. -8. Select the policy that you previously created and click **Create**. +8. Select the policy that you previously created and click **Create Policy Binding**. 9. Optionally, repeat the process for any other flows that you want the policy applied to. ### Checking Discord Guild role membership @@ -249,7 +249,7 @@ return user_matched 5. Click **Finish**. You can now bind this policy to the chosen enrollment and/or authentication flow of the Discord OAuth source. 6. Navigate to **Flows and Stages** > **Flows** and click the name of the flow in question. 7. Open the **Policy/Group/User Bindings** tab and click **Bind existing Policy/Group/User**. -8. Select the policy that you previously created and click **Create**. +8. Select the policy that you previously created and click **Create Policy Binding**. 9. Optionally, repeat the process for any other flows that you want the policy applied to. ## Resources diff --git a/website/docs/users-sources/sources/social-logins/entra-id/oauth/index.mdx b/website/docs/users-sources/sources/social-logins/entra-id/oauth/index.mdx index 930dbc45f5..23dda94764 100644 --- a/website/docs/users-sources/sources/social-logins/entra-id/oauth/index.mdx +++ b/website/docs/users-sources/sources/social-logins/entra-id/oauth/index.mdx @@ -56,7 +56,7 @@ To support the integration of Entra ID with authentik, you need to create an Ent ### Create Entra ID OAuth source 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Entra ID OAuth Source** as the source type. - **Create Entra ID OAuth Source**: provide a name, a slug which must match the slug used in the Entra ID `Redirect URI`, and the following required configurations: - Under **Protocol Settings**: diff --git a/website/docs/users-sources/sources/social-logins/entra-id/scim/index.mdx b/website/docs/users-sources/sources/social-logins/entra-id/scim/index.mdx index c31ce675e9..95349cc812 100644 --- a/website/docs/users-sources/sources/social-logins/entra-id/scim/index.mdx +++ b/website/docs/users-sources/sources/social-logins/entra-id/scim/index.mdx @@ -25,7 +25,7 @@ To integrate authentik with Entra ID via SCIM, you need to create a SCIM source ### Create SCIM source 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **SCIM Source**. - **Create SCIM Source**: provide a name and a slug. - All other configurations are optional. diff --git a/website/docs/users-sources/sources/social-logins/facebook/index.md b/website/docs/users-sources/sources/social-logins/facebook/index.md index 2d013882f0..8925651a2d 100644 --- a/website/docs/users-sources/sources/social-logins/facebook/index.md +++ b/website/docs/users-sources/sources/social-logins/facebook/index.md @@ -48,7 +48,7 @@ Finally, you need to publish the Facebook app. To support the integration of Facebook with authentik, you need to create a Facebook OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Facebook OAuth Source** as the source type. - **Create Facebook OAuth Source**: provide a name, a slug which must match the slug used in the Facebook `Valid OAuth redirect URIs` field (e.g. `facebook`), and the following required configurations: - **Protocol settings** diff --git a/website/docs/users-sources/sources/social-logins/github/index.mdx b/website/docs/users-sources/sources/social-logins/github/index.mdx index fc81f24542..8fa1a6875d 100644 --- a/website/docs/users-sources/sources/social-logins/github/index.mdx +++ b/website/docs/users-sources/sources/social-logins/github/index.mdx @@ -32,7 +32,7 @@ To integrate GitHub with authentik, you need to create an OAuth application in G To support the integration of GitHub with authentik, you need to create a GitHub OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **GitHub OAuth Source** as the source type. - **Create GitHub OAuth Source**: provide a name, a slug which must match the slug used in the GitHub `Authorization callback URL` field (e.g. `github`), and set the following required configurations: - **Protocol settings** diff --git a/website/docs/users-sources/sources/social-logins/google/cloud/index.md b/website/docs/users-sources/sources/social-logins/google/cloud/index.md index 8b375ee568..d36eb690b7 100644 --- a/website/docs/users-sources/sources/social-logins/google/cloud/index.md +++ b/website/docs/users-sources/sources/social-logins/google/cloud/index.md @@ -66,7 +66,7 @@ To integrate Google with authentik, you need to create a new project and OAuth c To support the integration of Google with authentik, you need to create a Google OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Google OAuth Source** as the source type. - **Create Google OAuth Source**: provide a name, a slug that must match the slug used in the Google `Authorized redirect URI` field (e.g. `google`), and set the following required configurations: - **Protocol settings** @@ -107,7 +107,7 @@ return False 5. Click **Finish**. You can now bind this policy to the chosen enrollment flow of the Google OAuth source. 6. Navigate to **Flows and Stages** > **Flows** and click the name of the flow in question. 7. Open the **Stage Bindings** tab, expand the policies bound to the first stage and click **Bind existing Policy/Group/User**. -8. Select the policy that you previously created and click **Create**. +8. Select the policy that you previously created and click **Create Policy Binding**. :::note If using the default enrollment flow the policy should be bound to the **default-source-enrollment-prompt** stage. Ensure that the policy comes before **default-source-enrollment-if-username**. diff --git a/website/docs/users-sources/sources/social-logins/google/workspace/index.md b/website/docs/users-sources/sources/social-logins/google/workspace/index.md index 8fc16604f0..d9b6733ad1 100644 --- a/website/docs/users-sources/sources/social-logins/google/workspace/index.md +++ b/website/docs/users-sources/sources/social-logins/google/workspace/index.md @@ -105,7 +105,7 @@ authentik is acting as both a Service Provider (SP) to Google and an Identity Pr ### Create a SAML source in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login** and click **Create**. +2. Navigate to **Directory** > **Federation and Social login** and click **New Source**. 3. Select **SAML Source** and configure the following settings: - Set **Name** to `Google Workspace`. - Set **Slug** to `google` (must match the slug used in Google Workspace ACS URL). diff --git a/website/docs/users-sources/sources/social-logins/keycloak/index.md b/website/docs/users-sources/sources/social-logins/keycloak/index.md index 8a7a2d5037..4d9f864bf7 100644 --- a/website/docs/users-sources/sources/social-logins/keycloak/index.md +++ b/website/docs/users-sources/sources/social-logins/keycloak/index.md @@ -88,7 +88,7 @@ Before configuring either service, you need to export the signing certificates f ### Create a SAML source in authentik -1. Navigate to **Directory** > **Federation and Social login** and click **Create**. +1. Navigate to **Directory** > **Federation and Social login** and click **New Source**. 2. Select **SAML Source** and configure the following settings: - Set **Name** to `Keycloak`. - Set **Slug** to `keycloak`. diff --git a/website/docs/users-sources/sources/social-logins/mailcow/index.md b/website/docs/users-sources/sources/social-logins/mailcow/index.md index 9734f61d7d..012b81b6d8 100644 --- a/website/docs/users-sources/sources/social-logins/mailcow/index.md +++ b/website/docs/users-sources/sources/social-logins/mailcow/index.md @@ -26,7 +26,7 @@ To integrate Mailcow with authentik you will need to create an OAuth application ## authentik configuration 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **OAuth Source** as the source type. - **Create OAuth Source**: provide a name, a slug which must match the slug used in the Mailcow `Redirect URI` field (e.g. `mailcow`), and set the following required configurations: - **Protocol settings** diff --git a/website/docs/users-sources/sources/social-logins/okta/index.md b/website/docs/users-sources/sources/social-logins/okta/index.md index a20e2af8eb..4292d3e51e 100644 --- a/website/docs/users-sources/sources/social-logins/okta/index.md +++ b/website/docs/users-sources/sources/social-logins/okta/index.md @@ -33,7 +33,7 @@ To integrate Okta with authentik you will need to create an App Integration in t To support the integration of Okta with authentik, you need to create an Okta OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Okta OAuth Source** as the source type. - **Create Okta OAuth Source**: provide a name, a slug which must match the slug used in the Okta Sign-in redirect URI field (e.g. `okta`), and the following required settings: - Under **Protocol settings**: diff --git a/website/docs/users-sources/sources/social-logins/plex/index.md b/website/docs/users-sources/sources/social-logins/plex/index.md index 51ae2fbde9..9af5b39b23 100644 --- a/website/docs/users-sources/sources/social-logins/plex/index.md +++ b/website/docs/users-sources/sources/social-logins/plex/index.md @@ -16,7 +16,7 @@ None To support the integration of Plex with authentik, you need to create a Plex source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Plex Source** as the source type. - **Create Plex Source**: provide a name, a slug, and set the following required configurations: - **Icon**: Optional icon or image shown for the source. See [File picker values](../../../../customize/file-picker.md). diff --git a/website/docs/users-sources/sources/social-logins/shibboleth/index.md b/website/docs/users-sources/sources/social-logins/shibboleth/index.md index b07926ac64..705bcd1765 100644 --- a/website/docs/users-sources/sources/social-logins/shibboleth/index.md +++ b/website/docs/users-sources/sources/social-logins/shibboleth/index.md @@ -23,7 +23,7 @@ To integrate Shibboleth with authentik you will need to create a SAML source in ### Create a SAML source in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login** and click **Create**. +2. Navigate to **Directory** > **Federation and Social login** and click **New Source**. 3. Select **SAML Source** and configure the following settings: - Set **Name** to `Shibboleth`. - Set **Slug** to `shibboleth` (this sets the slug used in Shibboleth's metadata url). diff --git a/website/docs/users-sources/sources/social-logins/telegram/index.md b/website/docs/users-sources/sources/social-logins/telegram/index.md index 1d6fb73eeb..06c48bfbf0 100644 --- a/website/docs/users-sources/sources/social-logins/telegram/index.md +++ b/website/docs/users-sources/sources/social-logins/telegram/index.md @@ -27,7 +27,7 @@ Now that the bot is configured you can proceed to creating a source in authentik ## authentik configuration 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Telegram** as the source type. - **Create Telegram Source**: provide a name, a slug, and the following required configurations: - **Bot username**: The username of your Telegram bot (e.g., `authentik_bot`). diff --git a/website/docs/users-sources/sources/social-logins/twitch/index.md b/website/docs/users-sources/sources/social-logins/twitch/index.md index 1ef949d3e9..0c85f5d782 100644 --- a/website/docs/users-sources/sources/social-logins/twitch/index.md +++ b/website/docs/users-sources/sources/social-logins/twitch/index.md @@ -34,7 +34,7 @@ To integrate Twitch with authentik you will need to create an OAuth application To support the integration of Twitch with authentik, you need to create an Twitch OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Twitch OAuth Source** as the source type. - **Create OAuth Source**: provide a name, a slug which must match the slug used in the Twitch `OAuth Redirect URLs` field (e.g. `twitch`), and set the following required configurations: - **Protocol settings** diff --git a/website/docs/users-sources/sources/social-logins/twitter/index.md b/website/docs/users-sources/sources/social-logins/twitter/index.md index a53d786231..8584f127ba 100644 --- a/website/docs/users-sources/sources/social-logins/twitter/index.md +++ b/website/docs/users-sources/sources/social-logins/twitter/index.md @@ -36,7 +36,7 @@ To integrate X with authentik you will need to create an OAuth application in th To support the integration of X with authentik, you need to create a Twitter OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **Twitter OAuth Source** as the source type. - **Create OAuth Source**: provide a name, a slug which must match the slug used in the X `Callback URI / Redirect URL` field (e.g. `x`), and set the following required configurations: - **Protocol settings** diff --git a/website/docs/users-sources/sources/social-logins/wechat/index.md b/website/docs/users-sources/sources/social-logins/wechat/index.md index eec37d03c5..0eda755a95 100644 --- a/website/docs/users-sources/sources/social-logins/wechat/index.md +++ b/website/docs/users-sources/sources/social-logins/wechat/index.md @@ -32,7 +32,7 @@ This integration uses the WeChat "Website Application" login flow (QR Code login To support the integration of WeChat with authentik, you need to create a WeChat OAuth source in authentik. 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Directory** > **Federation and Social login**, click **Create**, and then configure the following settings: +2. Navigate to **Directory** > **Federation and Social login**, click **New Source**, and then configure the following settings: - **Select type**: select **WeChat OAuth Source** as the source type. - **Create OAuth Source**: provide a name, a slug (e.g. `wechat`), and set the following required configurations: - **Protocol settings** diff --git a/website/integrations/chat-communication-collaboration/affine/index.md b/website/integrations/chat-communication-collaboration/affine/index.md index 932362ec06..c0ed4c3f70 100644 --- a/website/integrations/chat-communication-collaboration/affine/index.md +++ b/website/integrations/chat-communication-collaboration/affine/index.md @@ -28,7 +28,7 @@ To support the integration of AFFiNE with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/espo-crm/index.md b/website/integrations/chat-communication-collaboration/espo-crm/index.md index 4b13b898c8..00dfab13c4 100644 --- a/website/integrations/chat-communication-collaboration/espo-crm/index.md +++ b/website/integrations/chat-communication-collaboration/espo-crm/index.md @@ -32,7 +32,7 @@ To support the integration of EspoCRM with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/hedgedoc/index.md b/website/integrations/chat-communication-collaboration/hedgedoc/index.md index 965db681f8..4f9f612356 100644 --- a/website/integrations/chat-communication-collaboration/hedgedoc/index.md +++ b/website/integrations/chat-communication-collaboration/hedgedoc/index.md @@ -28,7 +28,7 @@ To support the integration of HedgeDoc with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/joplin/index.md b/website/integrations/chat-communication-collaboration/joplin/index.md index 6b419e162f..56fa99ee3d 100644 --- a/website/integrations/chat-communication-collaboration/joplin/index.md +++ b/website/integrations/chat-communication-collaboration/joplin/index.md @@ -51,7 +51,7 @@ To support the integration of Joplin with authentik, you need to create property ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/chat-communication-collaboration/kanboard/index.md b/website/integrations/chat-communication-collaboration/kanboard/index.md index 806d20e79e..5431ee8157 100644 --- a/website/integrations/chat-communication-collaboration/kanboard/index.md +++ b/website/integrations/chat-communication-collaboration/kanboard/index.md @@ -28,7 +28,7 @@ To support the integration of Kanboard with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/kimai/index.md b/website/integrations/chat-communication-collaboration/kimai/index.md index 90b2283429..d1def898fd 100644 --- a/website/integrations/chat-communication-collaboration/kimai/index.md +++ b/website/integrations/chat-communication-collaboration/kimai/index.md @@ -29,7 +29,7 @@ To support the integration of Kimai with authentik, you need to create an applic ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/chat-communication-collaboration/mailcow/index.md b/website/integrations/chat-communication-collaboration/mailcow/index.md index 0904408516..e805b97530 100644 --- a/website/integrations/chat-communication-collaboration/mailcow/index.md +++ b/website/integrations/chat-communication-collaboration/mailcow/index.md @@ -32,7 +32,7 @@ To support the integration of mailcow with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/mastodon/index.md b/website/integrations/chat-communication-collaboration/mastodon/index.md index e57ab6d0ad..4d3e5db8b8 100644 --- a/website/integrations/chat-communication-collaboration/mastodon/index.md +++ b/website/integrations/chat-communication-collaboration/mastodon/index.md @@ -28,7 +28,7 @@ To support the integration of Mastodon with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/matrix-synapse/index.md b/website/integrations/chat-communication-collaboration/matrix-synapse/index.md index 07a8aee3c6..740f2d5958 100644 --- a/website/integrations/chat-communication-collaboration/matrix-synapse/index.md +++ b/website/integrations/chat-communication-collaboration/matrix-synapse/index.md @@ -28,7 +28,7 @@ To support the integration of Matrix Synapse with authentik, you need to create ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/mautic/index.md b/website/integrations/chat-communication-collaboration/mautic/index.md index be3a1cbfdb..5f36c85b09 100644 --- a/website/integrations/chat-communication-collaboration/mautic/index.md +++ b/website/integrations/chat-communication-collaboration/mautic/index.md @@ -65,7 +65,7 @@ Because Mautic requires a first name and last name attribute, create two [SAML p ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. - **Choose a Provider**: select **SAML Provider** as the provider type. - **Configure the Provider**: diff --git a/website/integrations/chat-communication-collaboration/mobilizon/index.md b/website/integrations/chat-communication-collaboration/mobilizon/index.md index af95cd181a..8abe032130 100644 --- a/website/integrations/chat-communication-collaboration/mobilizon/index.md +++ b/website/integrations/chat-communication-collaboration/mobilizon/index.md @@ -28,7 +28,7 @@ To support the integration of Mobilizon with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/openproject/index.md b/website/integrations/chat-communication-collaboration/openproject/index.md index 98704e4d19..ad8daa97df 100644 --- a/website/integrations/chat-communication-collaboration/openproject/index.md +++ b/website/integrations/chat-communication-collaboration/openproject/index.md @@ -53,7 +53,7 @@ OpenProject requires a first and last name for each user. By default authentik o ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 Provider** as the provider type. diff --git a/website/integrations/chat-communication-collaboration/owncloud/index.md b/website/integrations/chat-communication-collaboration/owncloud/index.md index 007e578653..f1a5dc31ec 100644 --- a/website/integrations/chat-communication-collaboration/owncloud/index.md +++ b/website/integrations/chat-communication-collaboration/owncloud/index.md @@ -30,7 +30,7 @@ The configuration for each application is nearly identical, except for the **Cli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) You will need to repeat the process four times: once each for the Desktop application, Web UI, Android application, and iOS application. +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. You will need to repeat the process four times: once each for the Desktop application, Web UI, Android application, and iOS application. - **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. diff --git a/website/integrations/chat-communication-collaboration/placetel/index.md b/website/integrations/chat-communication-collaboration/placetel/index.md index 09cdb1e4e7..40d9cfdd81 100644 --- a/website/integrations/chat-communication-collaboration/placetel/index.md +++ b/website/integrations/chat-communication-collaboration/placetel/index.md @@ -28,7 +28,7 @@ To support the integration of Placetel with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** value as it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/chat-communication-collaboration/rocketchat/index.md b/website/integrations/chat-communication-collaboration/rocketchat/index.md index 0bedfd1e4c..939e8fbd94 100644 --- a/website/integrations/chat-communication-collaboration/rocketchat/index.md +++ b/website/integrations/chat-communication-collaboration/rocketchat/index.md @@ -32,7 +32,7 @@ To support the integration of Rocket.chat with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/roundcube/index.md b/website/integrations/chat-communication-collaboration/roundcube/index.md index 9d39f4563c..73a18c33de 100644 --- a/website/integrations/chat-communication-collaboration/roundcube/index.md +++ b/website/integrations/chat-communication-collaboration/roundcube/index.md @@ -53,7 +53,7 @@ To support the integration of Roundcube with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/seatable/index.md b/website/integrations/chat-communication-collaboration/seatable/index.md index 217ddb00d8..2905166072 100644 --- a/website/integrations/chat-communication-collaboration/seatable/index.md +++ b/website/integrations/chat-communication-collaboration/seatable/index.md @@ -32,7 +32,7 @@ To support the integration of SeaTable with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. - Set the **Launch URL** to `https://seatable.company/sso/`. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/chat-communication-collaboration/slack/index.md b/website/integrations/chat-communication-collaboration/slack/index.md index 1d7aceb955..2555acd0ac 100644 --- a/website/integrations/chat-communication-collaboration/slack/index.md +++ b/website/integrations/chat-communication-collaboration/slack/index.md @@ -45,7 +45,7 @@ To support the integration of Slack with authentik, you need to create an applic #### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/chat-communication-collaboration/writefreely/index.md b/website/integrations/chat-communication-collaboration/writefreely/index.md index fd985d7795..abd5ed3788 100644 --- a/website/integrations/chat-communication-collaboration/writefreely/index.md +++ b/website/integrations/chat-communication-collaboration/writefreely/index.md @@ -32,7 +32,7 @@ To support the integration of Writefreely with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/chat-communication-collaboration/zoom/index.md b/website/integrations/chat-communication-collaboration/zoom/index.md index b6c50f9b77..b9be3028ef 100644 --- a/website/integrations/chat-communication-collaboration/zoom/index.md +++ b/website/integrations/chat-communication-collaboration/zoom/index.md @@ -32,7 +32,7 @@ To support the integration of Zoom with authentik, you need to create an applica ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** 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: diff --git a/website/integrations/chat-communication-collaboration/zulip/index.md b/website/integrations/chat-communication-collaboration/zulip/index.md index 6d3374f665..d837e04e38 100644 --- a/website/integrations/chat-communication-collaboration/zulip/index.md +++ b/website/integrations/chat-communication-collaboration/zulip/index.md @@ -28,7 +28,7 @@ To support the integration of Zulip with authentik, you need to create an applic ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/cloud-providers/digitalocean/index.md b/website/integrations/cloud-providers/digitalocean/index.md index 882e3cab33..84b3ff6b60 100644 --- a/website/integrations/cloud-providers/digitalocean/index.md +++ b/website/integrations/cloud-providers/digitalocean/index.md @@ -58,7 +58,7 @@ To support the integration of DigitalOcean with authentik, you need to create a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/cloud-providers/hashicorp-cloud/index.md b/website/integrations/cloud-providers/hashicorp-cloud/index.md index b8cc3de543..6bc209d4a8 100644 --- a/website/integrations/cloud-providers/hashicorp-cloud/index.md +++ b/website/integrations/cloud-providers/hashicorp-cloud/index.md @@ -33,7 +33,7 @@ To support the integration of HashiCorp Cloud with authentik, you need to create ### Create an Application and Provider in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications** and click **Create with Provider**. +2. Navigate to **Applications** > **Applications** and click **New Application**. - **Application**: Provide a descriptive name, an optional group, and UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: Select **SAML Provider**. - **Configure the Provider**: diff --git a/website/integrations/cloud-providers/oracle-cloud/index.md b/website/integrations/cloud-providers/oracle-cloud/index.md index 4703696fd1..89b650e0e7 100644 --- a/website/integrations/cloud-providers/oracle-cloud/index.md +++ b/website/integrations/cloud-providers/oracle-cloud/index.md @@ -28,7 +28,7 @@ To support the integration of Oracle Cloud with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. - Optionally set the **Launch URL** to `https://cloud.oracle.com?tenant=friendly-tenant-name` where `friendly-tenant-name` is the name of the tenant used when logging in via the [Oracle Cloud website](https://cloud.oracle.com). diff --git a/website/integrations/cloud-providers/ovhcloud/index.md b/website/integrations/cloud-providers/ovhcloud/index.md index 0c9366e09e..eb032c1b5f 100644 --- a/website/integrations/cloud-providers/ovhcloud/index.md +++ b/website/integrations/cloud-providers/ovhcloud/index.md @@ -23,7 +23,7 @@ To support the integration of OVHcloud with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** 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: diff --git a/website/integrations/dashboards/homarr/index.md b/website/integrations/dashboards/homarr/index.md index 29385698ac..4ed90c1b83 100644 --- a/website/integrations/dashboards/homarr/index.md +++ b/website/integrations/dashboards/homarr/index.md @@ -28,7 +28,7 @@ To support the integration of Homarr with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/dashboards/linkwarden/index.md b/website/integrations/dashboards/linkwarden/index.md index 36215c9dce..d0b5cf7bb8 100644 --- a/website/integrations/dashboards/linkwarden/index.md +++ b/website/integrations/dashboards/linkwarden/index.md @@ -28,7 +28,7 @@ To support the integration of Linkwarden with authentik, you need to create an a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/coder/index.md b/website/integrations/development/coder/index.md index 4d34ccf906..aed2baf312 100644 --- a/website/integrations/development/coder/index.md +++ b/website/integrations/development/coder/index.md @@ -28,7 +28,7 @@ To support the integration of Coder with authentik, you need to create an applic ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/forgejo/index.md b/website/integrations/development/forgejo/index.md index e0170f1bc5..4d1d75b550 100644 --- a/website/integrations/development/forgejo/index.md +++ b/website/integrations/development/forgejo/index.md @@ -28,7 +28,7 @@ To support the integration of Forgejo with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/frappe/index.md b/website/integrations/development/frappe/index.md index e49b2b332b..07235d54db 100644 --- a/website/integrations/development/frappe/index.md +++ b/website/integrations/development/frappe/index.md @@ -33,7 +33,7 @@ To support the integration of Frappe with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/gitea/index.md b/website/integrations/development/gitea/index.md index ff699b2786..36981e0bab 100644 --- a/website/integrations/development/gitea/index.md +++ b/website/integrations/development/gitea/index.md @@ -28,7 +28,7 @@ To support the integration of Gitea with authentik, you need to create an applic ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/github-enterprise-cloud/index.md b/website/integrations/development/github-enterprise-cloud/index.md index b163c276bf..a55157349d 100644 --- a/website/integrations/development/github-enterprise-cloud/index.md +++ b/website/integrations/development/github-enterprise-cloud/index.md @@ -32,7 +32,7 @@ To support the integration of GitHub Enterprise Cloud with authentik, you need t ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** as the provider type. diff --git a/website/integrations/development/github-enterprise-emu/index.md b/website/integrations/development/github-enterprise-emu/index.md index e51d1b322d..049f4ee3fe 100644 --- a/website/integrations/development/github-enterprise-emu/index.md +++ b/website/integrations/development/github-enterprise-emu/index.md @@ -44,7 +44,7 @@ GitHub will create usernames for your EMU users based on the SAML `NameID` prope ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** as the provider type. diff --git a/website/integrations/development/github-enterprise-server/index.md b/website/integrations/development/github-enterprise-server/index.md index 8a163e3cf1..0cebbd8f1a 100644 --- a/website/integrations/development/github-enterprise-server/index.md +++ b/website/integrations/development/github-enterprise-server/index.md @@ -34,7 +34,7 @@ In order to use GitHub Enterprise Server, SCIM must also be set up. ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** as the provider type. diff --git a/website/integrations/development/github-organization/index.md b/website/integrations/development/github-organization/index.md index 702ca7af7d..8ec14dc3d1 100644 --- a/website/integrations/development/github-organization/index.md +++ b/website/integrations/development/github-organization/index.md @@ -28,7 +28,7 @@ To support the integration of GitHub Organization with authentik, you need to cr ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/development/gravitee/index.md b/website/integrations/development/gravitee/index.md index 9606623859..1aa221dd3c 100644 --- a/website/integrations/development/gravitee/index.md +++ b/website/integrations/development/gravitee/index.md @@ -30,7 +30,7 @@ To support the integration of Gravitee with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/jenkins/index.md b/website/integrations/development/jenkins/index.md index dad4ce91e5..7799e013af 100644 --- a/website/integrations/development/jenkins/index.md +++ b/website/integrations/development/jenkins/index.md @@ -28,7 +28,7 @@ To support the integration of Jenkins with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/node-red/index.md b/website/integrations/development/node-red/index.md index 9067255861..e7fd1e43ad 100644 --- a/website/integrations/development/node-red/index.md +++ b/website/integrations/development/node-red/index.md @@ -34,7 +34,7 @@ To support the integration of Node-RED with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/development/weblate/index.md b/website/integrations/development/weblate/index.md index df84766130..f4c229fe7d 100644 --- a/website/integrations/development/weblate/index.md +++ b/website/integrations/development/weblate/index.md @@ -66,7 +66,7 @@ To support the integration of Weblate with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/device-management/fleet/index.md b/website/integrations/device-management/fleet/index.md index 41ea864677..f88d33c7d1 100644 --- a/website/integrations/device-management/fleet/index.md +++ b/website/integrations/device-management/fleet/index.md @@ -33,7 +33,7 @@ The workflow to configure authentik as a single sign-on provider for Fleet invol ### Create an application and provider -1. From the authentik Admin interface, navigate to **Applications > Applications** and click **Create with Provider** to create an application and provider pair. +1. From the authentik Admin interface, navigate to **Applications > Applications** and click **New Application** to create an application and provider pair. 2. For the **App name** enter `Fleet` and click **Next**. diff --git a/website/integrations/device-management/meshcentral/index.md b/website/integrations/device-management/meshcentral/index.md index 03acce0906..5f15d06ee6 100644 --- a/website/integrations/device-management/meshcentral/index.md +++ b/website/integrations/device-management/meshcentral/index.md @@ -28,7 +28,7 @@ To support the integration of MeshCentral with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/dokuwiki/index.md b/website/integrations/documentation/dokuwiki/index.md index 87632720e1..196a697e96 100644 --- a/website/integrations/documentation/dokuwiki/index.md +++ b/website/integrations/documentation/dokuwiki/index.md @@ -28,7 +28,7 @@ To support the integration of DokuWiki with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. - _(Optional)_ Under **UI Settings**, set the **Launch URL** to `https://dokuwiki.company/doku.php?id=start&oauthlogin=generic`. This will allow you to log in directly to DokuWiki from the authentik applications dashboard and skip the DokuWiki OAuth Login button. diff --git a/website/integrations/documentation/glpi/index.md b/website/integrations/documentation/glpi/index.md index 0377897925..2630a37c30 100644 --- a/website/integrations/documentation/glpi/index.md +++ b/website/integrations/documentation/glpi/index.md @@ -82,7 +82,7 @@ To support the integration of GLPI with authentik, you need to create property m ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **Slug** value as it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/documentation/karakeep/index.md b/website/integrations/documentation/karakeep/index.md index a5909ba7b7..0eb32fbe3b 100644 --- a/website/integrations/documentation/karakeep/index.md +++ b/website/integrations/documentation/karakeep/index.md @@ -28,7 +28,7 @@ To support the integration of Karakeep with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/kitchenowl/index.md b/website/integrations/documentation/kitchenowl/index.md index 62652891dd..138f183da8 100644 --- a/website/integrations/documentation/kitchenowl/index.md +++ b/website/integrations/documentation/kitchenowl/index.md @@ -28,7 +28,7 @@ To support the integration of KitchenOwl with authentik, you need to create an a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **Slug** value as it will be required later. - **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. diff --git a/website/integrations/documentation/mealie/index.md b/website/integrations/documentation/mealie/index.md index bf4f580f54..d52669a4f4 100644 --- a/website/integrations/documentation/mealie/index.md +++ b/website/integrations/documentation/mealie/index.md @@ -28,7 +28,7 @@ To support the integration of Mealie with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/netbox/index.md b/website/integrations/documentation/netbox/index.md index 83cee9d548..2bed78d073 100644 --- a/website/integrations/documentation/netbox/index.md +++ b/website/integrations/documentation/netbox/index.md @@ -28,7 +28,7 @@ To support the integration of NetBox with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/outline/index.md b/website/integrations/documentation/outline/index.md index 54692ced69..cbdfe83b1e 100644 --- a/website/integrations/documentation/outline/index.md +++ b/website/integrations/documentation/outline/index.md @@ -29,7 +29,7 @@ To support the integration of Outline with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/tandoor/index.md b/website/integrations/documentation/tandoor/index.md index 8f7351dd3f..c02b2fbfb0 100644 --- a/website/integrations/documentation/tandoor/index.md +++ b/website/integrations/documentation/tandoor/index.md @@ -28,7 +28,7 @@ To support the integration of Tandoor with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/wiki-js/index.md b/website/integrations/documentation/wiki-js/index.md index a766dde80f..76bdb5090e 100644 --- a/website/integrations/documentation/wiki-js/index.md +++ b/website/integrations/documentation/wiki-js/index.md @@ -38,7 +38,7 @@ To support the integration of Wiki.js with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/documentation/youtrack/index.md b/website/integrations/documentation/youtrack/index.md index e5d598e928..e5980518b5 100644 --- a/website/integrations/documentation/youtrack/index.md +++ b/website/integrations/documentation/youtrack/index.md @@ -28,7 +28,7 @@ To support the integration of YouTrack with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** as the provider type. diff --git a/website/integrations/hypervisors-orchestrators/arcane/index.md b/website/integrations/hypervisors-orchestrators/arcane/index.md index 6fd5865d2d..10ea67efc9 100644 --- a/website/integrations/hypervisors-orchestrators/arcane/index.md +++ b/website/integrations/hypervisors-orchestrators/arcane/index.md @@ -48,7 +48,7 @@ Arcane either requires the email scope to return a `true` value for whether the ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/hypervisors-orchestrators/portainer/index.md b/website/integrations/hypervisors-orchestrators/portainer/index.md index 009792d426..1c69424181 100644 --- a/website/integrations/hypervisors-orchestrators/portainer/index.md +++ b/website/integrations/hypervisors-orchestrators/portainer/index.md @@ -32,7 +32,7 @@ To support the integration of Portainer with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/hypervisors-orchestrators/proxmox-ve/index.md b/website/integrations/hypervisors-orchestrators/proxmox-ve/index.md index 96908fafc6..1467504232 100644 --- a/website/integrations/hypervisors-orchestrators/proxmox-ve/index.md +++ b/website/integrations/hypervisors-orchestrators/proxmox-ve/index.md @@ -32,7 +32,7 @@ To support the integration of Proxmox with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/hypervisors-orchestrators/vmware-cloud-director/index.md b/website/integrations/hypervisors-orchestrators/vmware-cloud-director/index.md index b1c9c5c9a0..4943328a6f 100644 --- a/website/integrations/hypervisors-orchestrators/vmware-cloud-director/index.md +++ b/website/integrations/hypervisors-orchestrators/vmware-cloud-director/index.md @@ -26,7 +26,7 @@ To support the integration of VMware Cloud Director with authentik, you need to ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/hypervisors-orchestrators/vmware-vcenter/index.md b/website/integrations/hypervisors-orchestrators/vmware-vcenter/index.md index 249c774b5b..e135ff3ae9 100644 --- a/website/integrations/hypervisors-orchestrators/vmware-vcenter/index.md +++ b/website/integrations/hypervisors-orchestrators/vmware-vcenter/index.md @@ -30,7 +30,7 @@ To support the integration of vCenter with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/hypervisors-orchestrators/xen-orchestra/index.md b/website/integrations/hypervisors-orchestrators/xen-orchestra/index.md index 940efa0e43..40169d38ac 100644 --- a/website/integrations/hypervisors-orchestrators/xen-orchestra/index.md +++ b/website/integrations/hypervisors-orchestrators/xen-orchestra/index.md @@ -33,7 +33,7 @@ To support the integration of Xen Orchestra with authentik, you need to create a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/argocd/index.md b/website/integrations/infrastructure/argocd/index.md index 15899fca70..3b294fcd2d 100644 --- a/website/integrations/infrastructure/argocd/index.md +++ b/website/integrations/infrastructure/argocd/index.md @@ -28,7 +28,7 @@ To support the integration of ArgoCD with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/awx-tower/index.md b/website/integrations/infrastructure/awx-tower/index.md index 0a162f38d7..5f27e8be4e 100644 --- a/website/integrations/infrastructure/awx-tower/index.md +++ b/website/integrations/infrastructure/awx-tower/index.md @@ -32,7 +32,7 @@ To support the integration of AWX Tower with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/infrastructure/harbor/index.md b/website/integrations/infrastructure/harbor/index.md index 206206429c..a72c747676 100644 --- a/website/integrations/infrastructure/harbor/index.md +++ b/website/integrations/infrastructure/harbor/index.md @@ -28,7 +28,7 @@ To support the integration of Harbor with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/omni/index.md b/website/integrations/infrastructure/omni/index.md index 938e82c9ce..aabec44389 100644 --- a/website/integrations/infrastructure/omni/index.md +++ b/website/integrations/infrastructure/omni/index.md @@ -37,7 +37,7 @@ To support the integration of Omni with authentik, you need to create a property - **SAML Attribute Name**: `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name` - **Expression**: `return request.user.email` -3. Navigate to **Applications** > **Applications** and click **Create with Provider** to create an application and provider pair. (Alternatively you can first create a provider separately, then create the application and connect it with the provider.) +3. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, application slug, an optional group for the type of application, the policy engine mode, and optional UI settings. diff --git a/website/integrations/infrastructure/osticket/index.md b/website/integrations/infrastructure/osticket/index.md index 975764a908..87a19217a5 100644 --- a/website/integrations/infrastructure/osticket/index.md +++ b/website/integrations/infrastructure/osticket/index.md @@ -26,7 +26,7 @@ This documentation lists only the settings that you need to change from their de To support the integration of osTicket with authentik, you need to create an application/provider pair in authentik. 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/pgadmin/index.md b/website/integrations/infrastructure/pgadmin/index.md index 8ed159bf38..ee477ca3b9 100644 --- a/website/integrations/infrastructure/pgadmin/index.md +++ b/website/integrations/infrastructure/pgadmin/index.md @@ -32,7 +32,7 @@ To support the integration of pgAdmin with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/plesk/index.md b/website/integrations/infrastructure/plesk/index.md index d8f8726f2d..6cac3e64d2 100644 --- a/website/integrations/infrastructure/plesk/index.md +++ b/website/integrations/infrastructure/plesk/index.md @@ -32,7 +32,7 @@ To support the integration of Plesk with authentik, you need to create an applic ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/synology-dsm/index.md b/website/integrations/infrastructure/synology-dsm/index.md index 49915d4118..e7563c1156 100644 --- a/website/integrations/infrastructure/synology-dsm/index.md +++ b/website/integrations/infrastructure/synology-dsm/index.md @@ -32,7 +32,7 @@ To support the integration of Synology DSM with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/terraform-cloud/index.md b/website/integrations/infrastructure/terraform-cloud/index.md index a8d625e4bb..3dd2ed11ed 100644 --- a/website/integrations/infrastructure/terraform-cloud/index.md +++ b/website/integrations/infrastructure/terraform-cloud/index.md @@ -27,7 +27,7 @@ To support the integration of Terraform with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** 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: diff --git a/website/integrations/infrastructure/terrakube/index.md b/website/integrations/infrastructure/terrakube/index.md index 866af9a92b..57ec36fc08 100644 --- a/website/integrations/infrastructure/terrakube/index.md +++ b/website/integrations/infrastructure/terrakube/index.md @@ -28,7 +28,7 @@ To support the integration of Terrakube with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/truecommand/index.md b/website/integrations/infrastructure/truecommand/index.md index b3b384717a..3a0fb3e2aa 100644 --- a/website/integrations/infrastructure/truecommand/index.md +++ b/website/integrations/infrastructure/truecommand/index.md @@ -62,7 +62,7 @@ To support the integration of TrueCommand with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/infrastructure/zammad/index.md b/website/integrations/infrastructure/zammad/index.md index 297e4d7742..834c131add 100644 --- a/website/integrations/infrastructure/zammad/index.md +++ b/website/integrations/infrastructure/zammad/index.md @@ -44,7 +44,7 @@ To support the integration of Zammad with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. @@ -95,7 +95,7 @@ To support the integration of Zammad with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/infrastructure/zot/index.md b/website/integrations/infrastructure/zot/index.md index 754846a35f..62a65449d6 100644 --- a/website/integrations/infrastructure/zot/index.md +++ b/website/integrations/infrastructure/zot/index.md @@ -28,7 +28,7 @@ To support the integration of Zot with authentik, you need to create an applicat ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/media/audiobookshelf/index.md b/website/integrations/media/audiobookshelf/index.md index 0ba113feb5..6d3ebc263f 100644 --- a/website/integrations/media/audiobookshelf/index.md +++ b/website/integrations/media/audiobookshelf/index.md @@ -28,7 +28,7 @@ To support the integration of Audiobookshelf with authentik, you need to create ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/media/calibre-web/index.md b/website/integrations/media/calibre-web/index.md index 73b779f94e..266a34d3ed 100644 --- a/website/integrations/media/calibre-web/index.md +++ b/website/integrations/media/calibre-web/index.md @@ -28,7 +28,7 @@ To support the integration of Calibre-Web with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. diff --git a/website/integrations/media/emby/index.md b/website/integrations/media/emby/index.md index 5c0d04ad61..bdb9da13bb 100644 --- a/website/integrations/media/emby/index.md +++ b/website/integrations/media/emby/index.md @@ -34,7 +34,7 @@ This documentation lists only the settings that you need to change from their de ### LDAP provider configuration 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **LDAP Provider** as the provider type. - **Configure the Provider**: provide a name (or accept the auto-provided name) and the authorization flow to use for this provider. diff --git a/website/integrations/media/immich/index.md b/website/integrations/media/immich/index.md index d4b654f2f3..451fd6ba20 100644 --- a/website/integrations/media/immich/index.md +++ b/website/integrations/media/immich/index.md @@ -28,7 +28,7 @@ To support the integration of Immich with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/media/jellyseerr/index.md b/website/integrations/media/jellyseerr/index.md index d285761559..2cff8460ec 100644 --- a/website/integrations/media/jellyseerr/index.md +++ b/website/integrations/media/jellyseerr/index.md @@ -20,7 +20,7 @@ support_level: community To support the integration of Jellyseerr with authentik, you need to create an application/provider pair in authentik. 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, a slug, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **Slug** value as it will be required later. - **Choose a Provider type**: OAuth2/OpenID - **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and any required configurations. diff --git a/website/integrations/media/komga/index.md b/website/integrations/media/komga/index.md index 4cbabc7aa6..c8d1b6b99f 100644 --- a/website/integrations/media/komga/index.md +++ b/website/integrations/media/komga/index.md @@ -34,7 +34,7 @@ Refer to [Email scope verification](/docs/add-secure-apps/providers/oauth2/index ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/media/miniflux/index.md b/website/integrations/media/miniflux/index.md index 34c09d4ed0..6b1899ca17 100644 --- a/website/integrations/media/miniflux/index.md +++ b/website/integrations/media/miniflux/index.md @@ -28,7 +28,7 @@ To support the integration of Miniflux with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name (e.g., `Miniflux`), 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. diff --git a/website/integrations/media/seafile/index.md b/website/integrations/media/seafile/index.md index 975d50dca2..6ed3093ce6 100644 --- a/website/integrations/media/seafile/index.md +++ b/website/integrations/media/seafile/index.md @@ -27,7 +27,7 @@ To support the integration of Seafile with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/media/tautulli/index.md b/website/integrations/media/tautulli/index.md index 613b77571d..b6c1aa4618 100644 --- a/website/integrations/media/tautulli/index.md +++ b/website/integrations/media/tautulli/index.md @@ -47,7 +47,7 @@ Because Tautulli requires valid HTTP Basic credentials, you must save your HTTP ### Create an application and provider 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **Proxy Provider** as the provider type. diff --git a/website/integrations/miscellaneous/home-assistant/index.md b/website/integrations/miscellaneous/home-assistant/index.md index 8c6dab2fd5..d65c3954ff 100644 --- a/website/integrations/miscellaneous/home-assistant/index.md +++ b/website/integrations/miscellaneous/home-assistant/index.md @@ -47,7 +47,7 @@ To support the integration of Home Assistant with authentik, you need to create ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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** as the provider type. - Note the **Client ID**, **Client Secret**, and **slug** values because they will be required later. @@ -102,7 +102,7 @@ To support the integration of Home Assistant using `hass-auth-headers` with auth ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **Proxy** as the provider type. - **External Host**: Set this to the external URL you will be accessing Home Assistant from. diff --git a/website/integrations/miscellaneous/open-webui/index.md b/website/integrations/miscellaneous/open-webui/index.md index 7751703802..ea0f8c20e0 100644 --- a/website/integrations/miscellaneous/open-webui/index.md +++ b/website/integrations/miscellaneous/open-webui/index.md @@ -28,7 +28,7 @@ To support the integration of Open WebUI with authentik, you need to create an a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/miscellaneous/zipline/index.md b/website/integrations/miscellaneous/zipline/index.md index 9966f5da2f..ac4a3f45ba 100644 --- a/website/integrations/miscellaneous/zipline/index.md +++ b/website/integrations/miscellaneous/zipline/index.md @@ -32,7 +32,7 @@ To support the integration of Zipline with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/monitoring/glitchtip/index.md b/website/integrations/monitoring/glitchtip/index.md index 479484e9cd..fd21fda198 100644 --- a/website/integrations/monitoring/glitchtip/index.md +++ b/website/integrations/monitoring/glitchtip/index.md @@ -28,7 +28,7 @@ To support the integration of Glitchtip with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/monitoring/observium/index.md b/website/integrations/monitoring/observium/index.md index 9e50fde6e1..de5a473f34 100644 --- a/website/integrations/monitoring/observium/index.md +++ b/website/integrations/monitoring/observium/index.md @@ -45,7 +45,7 @@ To support the integration of Observium with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/monitoring/pulse/index.md b/website/integrations/monitoring/pulse/index.md index ac62debb1d..6841d98fac 100644 --- a/website/integrations/monitoring/pulse/index.md +++ b/website/integrations/monitoring/pulse/index.md @@ -28,7 +28,7 @@ To support the integration of Pulse with authentik, you need to create an applic ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/monitoring/ubuntu-landscape/index.md b/website/integrations/monitoring/ubuntu-landscape/index.md index 369a1ae007..936314bad7 100644 --- a/website/integrations/monitoring/ubuntu-landscape/index.md +++ b/website/integrations/monitoring/ubuntu-landscape/index.md @@ -34,7 +34,7 @@ To support the integration of Landscape with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/monitoring/uptime-kuma/index.md b/website/integrations/monitoring/uptime-kuma/index.md index c18a36da34..99fb5cf6db 100644 --- a/website/integrations/monitoring/uptime-kuma/index.md +++ b/website/integrations/monitoring/uptime-kuma/index.md @@ -30,7 +30,7 @@ To support the integration of Uptime Kuma with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **Proxy Provider** as the provider type. diff --git a/website/integrations/monitoring/whats-up-docker/index.md b/website/integrations/monitoring/whats-up-docker/index.md index 894e1c6d3f..9801fe88e1 100644 --- a/website/integrations/monitoring/whats-up-docker/index.md +++ b/website/integrations/monitoring/whats-up-docker/index.md @@ -28,7 +28,7 @@ To support the integration of What's Up Docker with authentik, you need to creat ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/monitoring/zabbix/index.md b/website/integrations/monitoring/zabbix/index.md index 1225e774d8..279918ce30 100644 --- a/website/integrations/monitoring/zabbix/index.md +++ b/website/integrations/monitoring/zabbix/index.md @@ -30,7 +30,7 @@ To support the integration of Zabbix with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/networking/aruba-orchestrator/index.md b/website/integrations/networking/aruba-orchestrator/index.md index 52d09c78b0..c685aa8a97 100644 --- a/website/integrations/networking/aruba-orchestrator/index.md +++ b/website/integrations/networking/aruba-orchestrator/index.md @@ -42,7 +42,7 @@ To support the integration of Aruba Orchestrator with authentik, you need to cre ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/networking/firezone/index.md b/website/integrations/networking/firezone/index.md index c5fced3695..975b4fd318 100644 --- a/website/integrations/networking/firezone/index.md +++ b/website/integrations/networking/firezone/index.md @@ -28,7 +28,7 @@ To support the integration of Firezone with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/networking/fortigate-admin/index.md b/website/integrations/networking/fortigate-admin/index.md index 2cc03e6126..28d86ec389 100644 --- a/website/integrations/networking/fortigate-admin/index.md +++ b/website/integrations/networking/fortigate-admin/index.md @@ -38,7 +38,7 @@ To support the integration of FortiGate with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** as the provider type. diff --git a/website/integrations/networking/fortigate-ssl/index.md b/website/integrations/networking/fortigate-ssl/index.md index fa37cd5ac9..d5d0df3850 100644 --- a/website/integrations/networking/fortigate-ssl/index.md +++ b/website/integrations/networking/fortigate-ssl/index.md @@ -43,7 +43,7 @@ To support the integration of FortiGate SSLVPN with authentik, you need to creat ### Create an application and provider in authentik 1. Log in to authentik as an admin and navigate to the Admin interface. -2. Navigate to **Applications** > **Applications** and click **Create with Provider** to create an application and provider pair. +2. Navigate to **Applications** > **Applications** and click **New Application** to create an application and provider pair. - **Application**: provide a descriptive name (e.g. "FortiGate SSLVPN"), an optional group for the type of application, the policy engine mode, and optional UI settings. - **Choose a Provider type**: select **SAML Provider from metadata** as the provider type. diff --git a/website/integrations/networking/fortimanager/index.md b/website/integrations/networking/fortimanager/index.md index bf348fa5aa..e4005754ce 100644 --- a/website/integrations/networking/fortimanager/index.md +++ b/website/integrations/networking/fortimanager/index.md @@ -28,7 +28,7 @@ To support the integration of FortiManager with authentik, you need to create an ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** as the provider type. diff --git a/website/integrations/networking/globalprotect/index.md b/website/integrations/networking/globalprotect/index.md index 6c2d0c38b9..9f5bbbc3b7 100644 --- a/website/integrations/networking/globalprotect/index.md +++ b/website/integrations/networking/globalprotect/index.md @@ -34,7 +34,7 @@ To support the integration of GlobalProtect with authentik, you need to create a ### Create an Application and Provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: Provide a descriptive name, an optional group, and UI settings. Take note of the **slug** as it will be required later. - **Choose a Provider type**: Select **SAML Provider**. - **Configure the Provider**: diff --git a/website/integrations/networking/gravity/index.md b/website/integrations/networking/gravity/index.md index da9db9f08b..2bf2d51ad9 100644 --- a/website/integrations/networking/gravity/index.md +++ b/website/integrations/networking/gravity/index.md @@ -32,7 +32,7 @@ To support the integration of Gravity with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/networking/headscale/index.md b/website/integrations/networking/headscale/index.md index bb2f317ec1..7f0629bef4 100644 --- a/website/integrations/networking/headscale/index.md +++ b/website/integrations/networking/headscale/index.md @@ -28,7 +28,7 @@ To support the integration of Headscale with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/networking/hoop.dev/index.md b/website/integrations/networking/hoop.dev/index.md index 4ba8752ce8..00c62d409a 100644 --- a/website/integrations/networking/hoop.dev/index.md +++ b/website/integrations/networking/hoop.dev/index.md @@ -28,7 +28,7 @@ To support the integration of Hoop.dev with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/networking/netbird/index.md b/website/integrations/networking/netbird/index.md index 56b9e4f4f6..3cf8d4027b 100644 --- a/website/integrations/networking/netbird/index.md +++ b/website/integrations/networking/netbird/index.md @@ -28,7 +28,7 @@ To support the integration of NetBird with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/networking/tailscale/index.md b/website/integrations/networking/tailscale/index.md index 413e101be3..a204254c5d 100644 --- a/website/integrations/networking/tailscale/index.md +++ b/website/integrations/networking/tailscale/index.md @@ -47,7 +47,7 @@ To support the integration of Tailscale with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/platforms/budibase/index.md b/website/integrations/platforms/budibase/index.md index 4fd6f505b1..7da45ddebb 100644 --- a/website/integrations/platforms/budibase/index.md +++ b/website/integrations/platforms/budibase/index.md @@ -28,7 +28,7 @@ To support the integration of Budibase with authentik, you need to create an app ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/platforms/drupal/index.md b/website/integrations/platforms/drupal/index.md index 8040fd3bdc..7aae929c25 100644 --- a/website/integrations/platforms/drupal/index.md +++ b/website/integrations/platforms/drupal/index.md @@ -33,7 +33,7 @@ To support the integration of Drupal with authentik, you need to create an appli ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. The **slug** will be used in URLs and should match the `drupal-slug` placeholder defined earlier. - **Choose a Provider type**: select **OAuth2/OpenID Provider** as the provider type. diff --git a/website/integrations/platforms/microsoft/index.md b/website/integrations/platforms/microsoft/index.md index 6651db7508..68d8e61bc1 100644 --- a/website/integrations/platforms/microsoft/index.md +++ b/website/integrations/platforms/microsoft/index.md @@ -108,7 +108,7 @@ If MFA is configured in Microsoft365, then you also need to create a property ma ### 4. Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **Slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/platforms/pocketbase/index.md b/website/integrations/platforms/pocketbase/index.md index 73d0da4249..a90f577e96 100644 --- a/website/integrations/platforms/pocketbase/index.md +++ b/website/integrations/platforms/pocketbase/index.md @@ -35,7 +35,7 @@ To support the integration of PocketBase with authentik, you need to create an a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/platforms/salesforce/index.md b/website/integrations/platforms/salesforce/index.md index 7f74f19143..e04905fcd4 100644 --- a/website/integrations/platforms/salesforce/index.md +++ b/website/integrations/platforms/salesforce/index.md @@ -79,7 +79,7 @@ Salesforce JIT provisioning requires specific SAML attributes to automatically c ### Create an application and provider in authentik 1. Log in to authentik as an administrator and open the authentik Admin interface. -2. Navigate to **Applications** > **Applications** and click **Create with Provider** to create an application and provider pair. +2. Navigate to **Applications** > **Applications** and click **New Application** to create an application and provider pair. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **Slug** as it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/platforms/wordpress/index.md b/website/integrations/platforms/wordpress/index.md index a2d7b9c79c..f9664bcc30 100644 --- a/website/integrations/platforms/wordpress/index.md +++ b/website/integrations/platforms/wordpress/index.md @@ -32,7 +32,7 @@ To support the integration of WordPress with authentik, you need to create an ap ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/security/cloudflare-access/index.md b/website/integrations/security/cloudflare-access/index.md index 73ed4e80d4..4f0895bba9 100644 --- a/website/integrations/security/cloudflare-access/index.md +++ b/website/integrations/security/cloudflare-access/index.md @@ -34,7 +34,7 @@ To support the integration of Cloudflare Access with authentik, you need to crea ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/security/hashicorp-vault/index.md b/website/integrations/security/hashicorp-vault/index.md index 699907a6ac..06d65aace9 100644 --- a/website/integrations/security/hashicorp-vault/index.md +++ b/website/integrations/security/hashicorp-vault/index.md @@ -32,7 +32,7 @@ To support the integration of Hashicorp Vault with authentik, you need to create ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/security/knocknoc/index.md b/website/integrations/security/knocknoc/index.md index db4ad671ee..98c6024e88 100644 --- a/website/integrations/security/knocknoc/index.md +++ b/website/integrations/security/knocknoc/index.md @@ -70,7 +70,7 @@ This example sets the session duration to 540 minutes. Change the value to match ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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 **SAML Provider** as the provider type. diff --git a/website/integrations/security/knowbe4/index.md b/website/integrations/security/knowbe4/index.md index f5b228d6a4..70fd2daee5 100644 --- a/website/integrations/security/knowbe4/index.md +++ b/website/integrations/security/knowbe4/index.md @@ -27,7 +27,7 @@ To support the integration of KnowBe4 with authentik, you need to create an appl ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Take note of the **slug** value because it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/security/macmon-nac/index.md b/website/integrations/security/macmon-nac/index.md index 070b765103..edb9d8a1f7 100644 --- a/website/integrations/security/macmon-nac/index.md +++ b/website/integrations/security/macmon-nac/index.md @@ -28,7 +28,7 @@ To support the integration of macmon NAC with authentik, you need to create an a ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. Note the **slug** value because it will be required later. - **Choose a Provider type**: select **SAML Provider** 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. diff --git a/website/integrations/security/vaultwarden/index.md b/website/integrations/security/vaultwarden/index.md index 45122afe48..86a5bb2ee1 100644 --- a/website/integrations/security/vaultwarden/index.md +++ b/website/integrations/security/vaultwarden/index.md @@ -48,7 +48,7 @@ Vaultwarden either requires the email scope to return a true value for whether t ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **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. diff --git a/website/integrations/template/service.md b/website/integrations/template/service.md index 4f74e64605..2f1a0ed323 100644 --- a/website/integrations/template/service.md +++ b/website/integrations/template/service.md @@ -30,7 +30,7 @@ _Any specific info about this integration can go here._ ### Create an application and provider in authentik 1. Log in to authentik as an administrator 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 first create a provider separately, then create the application and connect it with the provider.) +2. Navigate to **Applications** > **Applications** and click **New Application** to open the application wizard. - **Application**: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings. - _If there are any specific settings required, list them here. Refer to the [ownCloud integration documentation](https://github.com/goauthentik/authentik/blob/main/website/integrations/chat-communication-collaboration/owncloud/index.md) for a complex requirements example._ - **Choose a Provider type**: _If there is a specific provider type required, state that here._