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>
2.7 KiB
2.7 KiB
title, sidebar_label, tags, authentik_enterprise, authentik_version
| title | sidebar_label | tags | authentik_enterprise | authentik_version | |||||
|---|---|---|---|---|---|---|---|---|---|
| Fleet connector | Fleet connector |
|
true | 2026.2.0 |
Fleet is an open-source device management platform designed to monitor, manage, and secure large fleets of devices.
The Fleet connector reports device information from your Fleet deployment, and optionally auto-assigns users to devices.
Preparation
- Take note of your Fleet Server URL, which is typically the URL used to access your Fleet instance. Alternatively, you can find the URL by logging in to the Fleet admin panel and navigating to Settings > Organization settings > Fleet web address.
- Follow the Fleet documentation for creating an API-only user and take note of its API key.
:::warning No user API keys Do not use an API key from a normal user because these keys expire. :::
Configure the Fleet connector
Follow these instructions to configure the Fleet connector in authentik:
- Log in to authentik as an administrator and open the authentik Admin interface.
- Navigate to Endpoint Devices > Connectors and click New Endpoint Connector.
- 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.
- Fleet API Token: enter the API key of an API-only user.
- Map users: enable if you want users associated with the device in Fleet to be automatically given access to the device via the authentik Agent.
- Map teams to device access group: enable if you want groups associated with the device in Fleet to be automatically mapped to a device access group and given access to the device via the authentik Agent.
- Click Finish.
:::note The Map teams to device access group setting will not detect changes to a device's groups membership in Fleet. If the device's groups change, you will need to manually configure a device access group. :::
After creating the connector, it can be used in the Endpoint Stage. Refer to Device compliance policy for more information on using device facts from the connector in a flow.