mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-30 14:57:36 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
43 lines
1.6 KiB
Plaintext
43 lines
1.6 KiB
Plaintext
---
|
|
title: "LDAP Overview"
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to authenticate into KMS with LDAP."
|
|
---
|
|
|
|
<Info>
|
|
LDAP is a paid feature.
|
|
|
|
If you're using KMS Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting KMS,
|
|
then you should contact [email protected] to purchase an enterprise license to use it.
|
|
|
|
</Info>
|
|
|
|
You can configure your organization in KMS to have members authenticate with the platform via [LDAP](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol).
|
|
|
|
LDAP providers:
|
|
|
|
- Active Directory
|
|
- [JumpCloud LDAP](/documentation/platform/ldap/jumpcloud)
|
|
- AWS Directory Service
|
|
- Foxpass
|
|
|
|
Read the general instructions for configuring LDAP [here](/documentation/platform/ldap/general).
|
|
|
|
If the documentation for your required identity provider is not shown in the list above, please reach out to [[email protected]](mailto:[email protected]) for assistance.
|
|
|
|
## FAQ
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="Why does KMS require additional email verification for users connected via LDAP?">
|
|
By default, KMS Cloud is configured to not trust emails from external
|
|
identity providers to prevent any malicious account takeover attempts via
|
|
email spoofing. Accordingly, KMS creates a new user for anyone provisioned
|
|
through an external identity provider and requires an additional email
|
|
verification step upon their first login.
|
|
|
|
If you're running a self-hosted instance of KMS and would like it to trust emails from external identity providers,
|
|
you can configure this behavior in the Server Admin Console.
|
|
|
|
</Accordion>
|
|
</AccordionGroup>
|