From 49df3cb3c4600baabff51fc769263f3ab80de5d0 Mon Sep 17 00:00:00 2001 From: tedstriker Date: Tue, 28 Nov 2023 21:56:56 +0100 Subject: [PATCH] Documentation: Added note for necessary unigue base DNs (#7717) * Added note for necessary unigue base DNs Added information, that every LDAP provider needs to have a unique base DN. Related to #7714 Signed-off-by: tedstriker * Update website/docs/providers/ldap/index.md Thank's for fixing the grammar ;) Co-authored-by: Tana M Berry Signed-off-by: tedstriker --------- Signed-off-by: tedstriker Co-authored-by: Tana M Berry --- website/docs/providers/ldap/index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/docs/providers/ldap/index.md b/website/docs/providers/ldap/index.md index 7163bb2dd..a2cf4f490 100644 --- a/website/docs/providers/ldap/index.md +++ b/website/docs/providers/ldap/index.md @@ -16,6 +16,10 @@ You can configure under which base DN the information should be available. For t Users are available under `ou=users,` and groups under `ou=groups,`. To aid compatibility, each user belongs to its own "virtual" group, as is standard on most Unix-like systems. This group does not exist in the authentik database, and is generated on the fly. These virtual groups are under the `ou=virtual-groups,` DN. +:::info +Note: Every LDAP provider needs to have a unique base DN. You can achieve this by prepending an application-specific OU or DC. e.g. `OU=appname,DC=ldap,DC=goauthentik,DC=io` +::: + The following fields are currently sent for users: - `cn`: User's username