mirror of
https://github.com/goauthentik/authentik.git
synced 2026-06-17 19:09:11 +03:00
Dominic R
7bdbfade30
* website/docs: add Splunk event forwarding docs Add Splunk HEC event forwarding under system event docs and keep the Splunk integration guide focused on SAML. Closes: #22223 Agent-thread: https://sdko.org/internal/thr/ak/019ea8d4-d4e4-7fc3-b3b6-aa8a16bd8d40 A7k-product: product A7k-product-repo: 3 Co-authored-by: Agent <agent@svc.sdko.net> * website/docs: move Splunk event forwarding guide Move the Splunk event forwarding guide into integrations and add an Events log forwarding overview that links to it. Agent-thread: https://sdko.org/internal/thr/ak/019eb29e-1b34-7681-b887-e03907dac184 A7k-product: product A7k-product-repo: 3 Co-authored-by: Agent <agent@svc.sdko.net> * website/integrations: remove Splunk HEC port Use the generic splunk.company HEC endpoint in the Splunk event forwarding guide instead of hardcoding a deployment-specific port. Agent-thread: https://sdko.org/internal/thr/ak/019eb29e-1b34-7681-b887-e03907dac184 A7k-product: product A7k-product-repo: 3 Co-authored-by: Agent <agent@svc.sdko.net> * Update website/docs/sys-mgmt/events/log-forwarding.mdx Signed-off-by: Dewi Roberts <dewi@goauthentik.io> --------- Signed-off-by: Dewi Roberts <dewi@goauthentik.io> Co-authored-by: Agent <agent@svc.sdko.net> Co-authored-by: Dewi Roberts <dewi@goauthentik.io>
29 lines
1.8 KiB
Plaintext
29 lines
1.8 KiB
Plaintext
---
|
|
title: Integrations overview
|
|
sidebar_label: Overview
|
|
sidebar_position: 1
|
|
---
|
|
|
|
## What is an integration?
|
|
|
|
An integration is how authentik connects to third-party applications, directories, and other identity providers.
|
|
Integrations can cover application access, source authentication, directory synchronization, provisioning, and operational workflows such as log forwarding.
|
|
|
|
### Applications
|
|
|
|
Applications include vendor tools such as Google Workspace, GitHub, Slack, or AWS. These applications can be integrated with authentik to provide single sign-on, provisioning, policy-based access, or other workflow-specific connections.
|
|
|
|
If you want to integrate an application that isn't listed, authentik can be configured to work with most applications that support authentication protocols such as [SAML](/docs/add-secure-apps/providers/saml), [OAuth and OpenID Connect](/docs/add-secure-apps/providers/oauth2).
|
|
|
|
To learn more, refer to the [Applications](./applications.mdx) page.
|
|
|
|
### Federated and social sources
|
|
|
|
Sources let authentik use external user credentials for authentication. Supported source integrations include federated directories like Active Directory and social logins such as Facebook and Twitter. These integrations support all major protocols, including [LDAP](/docs/users-sources/sources/protocols/ldap), [SCIM](/docs/users-sources/sources/protocols/scim), [SAML](/docs/users-sources/sources/protocols/saml), and [OAuth and OpenID Connect](/docs/users-sources/sources/protocols/oauth).
|
|
|
|
To learn more, refer to the [Sources](/docs/users-sources/sources) page.
|
|
|
|
### Operational integrations
|
|
|
|
Operational integrations connect authentik to systems that support administration, monitoring, compliance, and automation. These guides can include log forwarding, machine-to-machine identity, or product-specific configuration that is not limited to user authentication.
|