Difference between revisions of "External LDAP authentication with zimbraAuthLdapExternalDn"

(Solution)
(Solution)
Line 16: Line 16:
 
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.   
 
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:
+
'''How to steps:'''
  
 
1. Create user test@example.com
 
1. Create user test@example.com
Line 23: Line 23:
  
  
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

Revision as of 22:51, 23 September 2015

How to configure external LDAP authentication with zimbraAuthLdapExternalDn

   KB 22350        Last updated on 2015-09-23  




5.00
(one vote)


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

Ext1.jpeg


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
     example for zimbraAuthLdapBindDn: uid=%u,ou=people,%D  (whatever LDAP DIT structure they are using)



2. Create a user in AD.

Ext2.jpeg



3. View of the AD user from Softerra LDAP browser.

Ext3.jpeg



4. After the above steps are completed we can test the configuration by logging with the zimbra user that does not exists in AD.

Jump to: navigation, search