From 6224f7d41240f9eddc2f36486d3e4b9b3cd44402 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Simonyi=20Gerg=C5=91?= <28359278+gergosimonyi@users.noreply.github.com> Date: Mon, 28 Oct 2024 16:53:27 +0100 Subject: [PATCH] reword Kerberos MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Jens L. Signed-off-by: Simonyi Gergő <28359278+gergosimonyi@users.noreply.github.com> --- website/docs/releases/2024/v2024.10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/releases/2024/v2024.10.md b/website/docs/releases/2024/v2024.10.md index 4367ea5bd026..5fdb689a9a7e 100644 --- a/website/docs/releases/2024/v2024.10.md +++ b/website/docs/releases/2024/v2024.10.md @@ -14,7 +14,7 @@ To try out the release candidate, replace your Docker image tag with the latest - **Chrome Device Trust** Enterprise Preview: Verify that your users are logging in from managed devices and validate the devices' compliance with company policies. - **FIPS/FAL3 for FedRAMP "very high" compliance** Enterprise+: with support for SAML encryption and now JWE (JSON Web Encryption) support, authentik can now be configured for FIPS compliance at Federal Assurance Level (FAL) 3. - **Captcha on Identification stage**: Run a CAPTCHA process in the background while the user is entering their identification. -- **Kerberos source**: authentik can now integrate with existing Kerberos environments by allowing users to log in with their Kerberos credentials or SPNEGO or syncing users into authentik. +- **Kerberos source**: authentik can now integrate with existing Kerberos environments by allowing users to log in with their Kerberos credentials, SPNEGO or syncing users into authentik. ## Breaking changes