[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: connect to MS Exchange ldap
From: |
Josh Huber |
Subject: |
Re: connect to MS Exchange ldap |
Date: |
Mon, 28 Jun 2004 15:30:56 -0400 |
User-agent: |
Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) |
Kai Grossjohann <kai@emptydomain.de> writes:
> Emacs (and XEmacs) comes with EUDC, the Emacs Unified Directory
> Client. You can tell it to query both LDAP and BBDB. (Alas, I
> haven't been able to figure out, how. Must be me not being
> able to grok the docs.) It has a command eudc-expand-inline
> which fills the role of bbdb-complete-name.
I managed to get this working with XEmacs here at work, with the
following configuration:
1) ~/.eudc-options (this is generated by filling in an EUDC form,
where I just filled in the name of our AD domain controller):
;; This file was automatically generated by eudc.el.
(provide 'eudc-options-file)
(eudc-set-server "dc2.company.com" 'ldap t)
(setq eudc-server-hotlist 'nil)
2) Since I don't use bbdb at work, and just use the LDAP
directory for addresses, I used the following:
(eval-after-load
"message"
'(setq message-completion-alist
("^\\(Resent-\\)?\\(To\\|B?Cc\\):" . eudc-expand-inline)))
3) Then, I used the following ldap parameters:
(setq ldap-host-parameters-alist
'(("dc2.company.com" base
"dc=company,dc=com" binddn "jhuber@company.com" passwd
"**PASSWORD**" auth simple)))
4) Finally, I have the following parameters which were tweaked
using custom, to allow matching for the various fields in the
AD schema, and to specify the expansion format/behavior for
eudc lookups:
'(eudc-expansion-overwrites-query t)
'(eudc-inline-query-format (quote ((sn) (givenName) (givenName
sn) (mailNickname) (sAMAccountName))))
'(eudc-strict-return-matches nil)
'(eudc-inline-expansion-format (quote ("%s <%s>" cn email)))
It's been quite a while since I set this up (almost 2 years
now), but it's worked ever since. Hope that helps someone...
BTW, I was able to obtain kerberos tickets from the AD KDC, but
I have been (so far) unable to use them to authenticate to the
LDAP service, so I resorted using simple auth.
--
Josh Huber