How to use a different LDAP login?

D

Disgusted

Setup an Exchange account.
Now, Entourage assumes that your Exchange login is your login for
EVERYTHING, including LDAP. Our LDAP server is actually offloaded to the
central LDAP server (OpenLDAP?) - our Exchange server is only departmental...

That means that I can not access LDAP b/c Entourage tries to use my local
Exchange login on our centralized (and with DIFFERENT credentials) LDAP
server.
:^(

Is there any way to tell it to use its own login, just like you could do
with SMTP Auth?
If not, there's a feature request easily remedied by copying and pasting the
SMTP Auth code over to LDAP...(and testing it)!
:^)

I know you can uncheck a box to not login to LDAP at all, but that only
works if a login is not required for LDAP info. (wishful thinking).
Speaking of which, you can already do this in Outlook, since it allows
completely separate configuration of email accounts vs. address books.
 
C

Corentin Cras-Méneur

Disgusted said:
Is there any way to tell it to use its own login, just like you could do
with SMTP Auth?
Click to expand...

Add a new LDAP server in your accounts (in the Directory Services tab).
That should do the trick,


Corentin
 
D

Disgusted

Interesting.
I set that up and it *DID* work even without a login. However, even if I
override the port in the Exchange account's LDAP settings in the "Advanced"
tab to 636 --from the apparent Exchange default of 3269-- (636 works fine for
the "Directory Services" account) and otherwise mirror the same settings,
then it still fails with a "Error -17768."
Is this "Advanced" tab area just hopelessly proprietary for an Exchange-only
LDAP implementation (forcing me to create an external LDAP account under
Directory Services as you suggested and which worked), or should I be able to
use my own LDAP server settings inside the Exchange account settings (but am
missing something)?

If the former, as I suspect, then why? I thought LDAP was a standard to
which all LDAP servers basically adhere...? Also, when using the wizard to
create an Exchange account, it's quite obtuse about INSISTING on an LDAP
server entry, which is what got me started on all of this in the first
place...!
 
M

Mickey Stevens

Interesting.
I set that up and it *DID* work even without a login. However, even if I
override the port in the Exchange account's LDAP settings in the "Advanced"
tab to 636 --from the apparent Exchange default of 3269-- (636 works fine for
the "Directory Services" account) and otherwise mirror the same settings,
then it still fails with a "Error -17768."
Is this "Advanced" tab area just hopelessly proprietary for an Exchange-only
LDAP implementation (forcing me to create an external LDAP account under
Directory Services as you suggested and which worked), or should I be able to
use my own LDAP server settings inside the Exchange account settings (but am
missing something)?
Click to expand...

Yes, there is something unique about the LDAP interface in the Exchange
account settings. Actually, before the Exchange account type was available
in Entourage, users could not connect to Microsoft Exchange LDAP servers
using normal Directory Service accounts in Entourage because Exchange LDAP
servers use some sort of special authentication scheme that's not used by
standard LDAP servers. You were probably getting that error because your
OpenLDAP server was rejecting the special authentication.
 
Top