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 <github@meins.org> * Update website/docs/providers/ldap/index.md Thank's for fixing the grammar ;) Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com> Signed-off-by: tedstriker <github@meins.org> --------- Signed-off-by: tedstriker <github@meins.org> Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
This commit is contained in:
parent
52e4a008d5
commit
49df3cb3c4
|
@ -16,6 +16,10 @@ You can configure under which base DN the information should be available. For t
|
||||||
|
|
||||||
Users are available under `ou=users,<base DN>` and groups under `ou=groups,<base DN>`. 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,<base DN>` DN.
|
Users are available under `ou=users,<base DN>` and groups under `ou=groups,<base DN>`. 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,<base DN>` 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:
|
The following fields are currently sent for users:
|
||||||
|
|
||||||
- `cn`: User's username
|
- `cn`: User's username
|
||||||
|
|
Reference in New Issue