Skip to content
MSO CloudDocumentation

Set up LDAP/AD login

On this page

Members sign in with their directory password; the platform keeps deciding role, capabilities and brand access.

Who can do this: a super admin for step 1; a role with the organization-settings capability for the rest.

Before you start#

  • The directory accepts LDAPS or STARTTLS from the platform and sits on a real address: loopback, link-local, unspecified and platform-internal ranges are refused.
  • Members who sign in with a Google or Microsoft account use OpenID Connect login instead, configured on its own settings tab.
LDAP login"Đăng nhập LDAP"tab shown once a super admin enables directory login1ServerServer addressldap.example.comPort636Connection securityLDAPSSTARTTLSno unencrypted optionAccept self-signed TLS certificates2Service accountBind DNcn=service-account,dc=example,dc=comLeave empty if the server allows an anonymous bind.Bind password••••••••Blank while editing keeps the saved password.3User searchBase DN #1ou=staff,dc=example,dc=comBase DN #2ou=contractors,dc=example,dc=comAdd a pathup to 10 pathsSearch filter(uid={{username}})must contain {{username}}Email attributemailDisplay name attributecn4Save changes5Test connection6tests the last SAVED configuration; result: connected, unreachable,TLS error, bind failed, base not found, timeoutThe whole directory sequence (connect, TLS, bind, search, bind) must finish within 5 s.
Settings > LDAP login. Callout N marks the control used in step N.

Steps#

  1. A super admin opens the organization's record at Customers > Organizations and turns on Enable LDAP login. The tab stays hidden until then.
  2. Open Settings > LDAP login ("Cài đặt > Đăng nhập LDAP") and fill Server: address, port, LDAPS or STARTTLS. Tick the self-signed switch only for a certificate the directory team cannot replace.
  3. Fill Service account: Bind DN and password, or leave both empty for an anonymous bind. While editing, an empty password keeps the saved one.
  4. Fill User search: up to 10 Base DN paths, a filter containing {{username}}, and the attributes carrying email and display name.
  5. Press Save changes.
  6. Press Test connection. It runs against the saved configuration and names the failing stage: unreachable, TLS, bind, base DN, timeout. Success reads "Connected successfully."
  7. Check with a member who already has a platform account: they sign in with directory credentials and land with the role set on the platform.

If it fails#

Symptom Cause Fix
LDAP login tab missing, or no form Directory login not enabled for the organization Ask a super admin (step 1).
A directory account cannot sign in No platform account carries that email Invite the member first; directory login never creates an account.
Member of several organizations refused Directory login is for people in exactly one organization They sign in with a password, passkey or one-time link.
Server address rejected on save Loopback, link-local, unspecified or platform-internal range Use the directory's real external address.
"The server did not respond in time" The whole sequence must finish within 5 seconds Check port and firewall; shorten the Base DN list.