With the red we see where to write the bindDN of the account we will use for the setup. More information on the syntax of this value can be found in /opt/zimbra/docs/externalldapauth.txt. Excerpt from that file:

With the red we see where to write the bindDN of the account we will use for the setup. More information on the syntax of this value can be found in /opt/zimbra/docs/externalldapauth.txt. Excerpt from that file:

+

+

Account attribute zimbraAuthLdapExternalDn

Account attribute zimbraAuthLdapExternalDn

Unlike (A) and (B), which are domain settings, this is an account level setting.

Unlike (A) and (B), which are domain settings, this is an account level setting.

- This article is a Community contribution and may include unsupported customizations.

External LDAP authetication ( zimbraAuthLdapExternalDn )

More information on how to configure Zimbra with AD can be found: [here]

Solution

The idea behind this type of authentication is to use a zimbra user that does not exists in AD, but at the same time to be able to login to his WebUI using already existing AD user.

How to steps:

1. Create user test@example.com

With the red we see where to write the bindDN of the account we will use for the setup. More information on the syntax of this value can be found in /opt/zimbra/docs/externalldapauth.txt. Excerpt from that file:

Account attribute zimbraAuthLdapExternalDn
Unlike (A) and (B), which are domain settings, this is an account level setting.
This overrides the bind template and/or search setting, and directly contains the DN for the user in the external ldap server.
zimbraAuthLdapBindDn and zimbraAuthLdapSearchFilter can contain expansion variables that are to be substituted by components in the account name:
%n = username with @ (or without, if no @ was specified)
%u = username with @ removed
%d = domain as foo.com
%D = domain as dc=foo,dc=com
e.g. for user pshao@zimbra.com
%n => pshao@zimbra.com
%u => pshao
%d => zimbra.com
%D => dc=zimbra,dc=com