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.3 KiB
title, sidebar_label, tags, authentik_version
| title | sidebar_label | tags | authentik_version | ||||
|---|---|---|---|---|---|---|---|
| authentik Agent connector | authentik Agent connector |
|
2025.12.0 |
The authentik Agent connector allows device information to be reported by the authentik Agent.
Unlike other connectors, the agent connector is used directly by the agent itself, rather than communicating with external systems or APIs. As a result, its behavior and functionality differ from those of other connectors.
The agent connector mainly holds configuration for the agent itself, as well as implementing certain platform-specific protocols like Apple's Platform SSO.
Configure the authentik Agent connector
Follow these instructions to configure the authentik Agent connector:
- Log in to authentik as an administrator and open the authentik Admin interface.
- Navigate to Endpoint Devices > Connectors and click New Endpoint Connector.
- 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.
- Enabled: enable or disable the connector.
- Click Finish.
Configure Challenge Key
The Agent connector requires a Challenge Key (certificate keypair) to be configured when using the Endpoint Stage. This keypair is used to sign challenges sent to the browser extension for device verification.
Without a Challenge Key configured, the Endpoint Stage will silently skip device verification.
To configure a Challenge Key:
- Navigate to System > Certificates and create a new certificate keypair, or select an existing one.
- Navigate to Endpoint Devices > Connectors and edit your Agent connector.
- Set the Challenge Key field to your certificate keypair.
- Click Update.
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.