mirror of
https://github.com/goauthentik/authentik
synced 2026-04-27 09:57:31 +02:00
6ed5cb5249
* website/integrations: rename "Create with Provider" to "New Application" The application list page now uses a split-button labeled "New Application" instead of the old "Create with Provider" dropdown. Update all 113 integration guides to match. * website/docs: update flow, stage, and policy button labels - "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons - "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit - "Create and bind stage" → "New Stage" / "Bind Existing Stage" - "Create" (binding submit) → "Create Stage Binding" * website/docs: update provider button labels - "Create" → "New Provider" for trigger buttons - "Create with Provider" → "New Application" in RAC docs - "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt" for related entity creation * website/docs: update directory button labels - "Create" → "New Source" for federation/social login pages - "Create" → "New Role", submit → "Create Role" - "Create" → "New Invitation" - Policy binding submit → "Create Policy Binding" * website/docs: update endpoint device and system management button labels - "Create" → "New Endpoint Connector", "New Enrollment Token", "New Device Access Group", "New Flow" - Submit → "Create Device Access Group" - "Create" → "New Notification Rule", "New Notification Transport" - Binding submit → "Create Policy Binding" * Reorganize policy documentation * website/docs: address policy docs review feedback * post-rebase * website/docs: Reorganize policy documentation -- Revisions (#21601) * apply suggestions * Fix escaped. * Fix whitespace. * Update button label. * Fix phrasing. * Fix phrasing. * Clean up stragglers. * Format. --------- Co-authored-by: Dominic R <dominic@sdko.org>
52 lines
2.7 KiB
Markdown
52 lines
2.7 KiB
Markdown
---
|
|
title: Linux local device login
|
|
sidebar_label: Linux
|
|
tags: [authentik Agent, device login, device authentication, linux]
|
|
authentik_enterprise: true
|
|
authentik_version: "2025.12.0"
|
|
---
|
|
|
|
<!-- TODO @BeryJu add screenshot -->
|
|
|
|
## Prerequisites
|
|
|
|
- The authentik Agent deployed on the Linux device. See [Deploy the authentik Agent on Linux](../../agent-deployment/linux.mdx) for more details.
|
|
- A **[Device access group](../device-access-groups.mdx)** configured with the appropriate user or group bindings. Without this, all login attempts will be denied. See [Configure device access](#configure-device-access) below.
|
|
|
|
## How it works
|
|
|
|
- authentik Agent is integrated with the Pluggable Authentication Modules (PAM) framework on the Linux device.
|
|
- The end user logs in via the usual Linux login screen but are prompted for their authentik credentials.
|
|
- The Agent authenticates the credentials against the authentik server and the user is logged in.
|
|
|
|
## How to log in to a Linux device
|
|
|
|
:::note
|
|
When configured correctly, when logging in you should see a prompt for **authentik Password** rather than just **Password**.
|
|
:::
|
|
|
|
1. On the Linux login screen, you enter your authentik credentials.
|
|
2. Once authenticated, you will be logged in to the Linux device.
|
|
|
|
## Configure device access
|
|
|
|
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 **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**.
|
|
6. Navigate to **Endpoint Devices** > **Devices** and edit the device for which you want to enable login.
|
|
7. Set the **Access group** to the device access group you created.
|
|
8. Click **Update**.
|
|
|
|
:::info
|
|
You can also assign a device access group during enrollment by selecting a **Device group** when creating the enrollment token.
|
|
:::
|
|
|
|
## Known issues
|
|
|
|
- Only Webauthn MFA is supported.
|
|
- On non-Debian Linux distributions, you currently need to [manually configure NSS and PAM](../../agent-deployment/linux.mdx#configure-device-login-on-non-debian-systems).
|