Hello all
How to correctly configure GAL Ldap auth in connector profile while MS is configured in hosted domain mode?
I need something like this insted of %s pattern
uid=%USER_PART,ou=people,o=%DOMAIN_PART,dc=comstar,dc=ru
Maybe this problem may be solved with LDAP Proxy? Does it support bind rewrite operation?
Any ideas? Maybe I've missed something?
Thanx in advance
Honestly, I haven't a clue what you're doing.
Please do start with:
version of messaging server.
And, I am not familiar with GAL Ldap auth, at all. Makes it harder for me to be of much help.
As for solving this with ldap proxy? I dunno. I'd be asking that in the ldap forum.
Thanx Jay!
Ok, I'll try to explain :)
Versions of all server components (MS, CE, Calendar, LDAP) - 2005Q4, Connector - 7.1.225.0
GAL throught connector it's a simple LDAP search with auth to LDAP server
The main problem that MS is configured in hosted domain mode, so every domain reside in such kind of branch
o=domain_name,dc=comstar,dc=ru (dc=comstar,dc=ru it's a base search DN)
In connector deployment program I have to configure pattern for auth users (BIND operation) before to perform
searches. Because I'm creating deployment profile for all domains I need someting like this
uid=%USER_PART,ou=people,o=%DOMAIN_PART,dc=comstar,dc=ru
But in the documentation of the connector I see:
-
User DN pattern: The elements of the user抯 Distinguished Name that, when
assembled, will form the complete DN to authenticate the user抯 identity to the
LDAP Directory Service (if authentication is required). For example, to define a DN
consisting of a user ID (uid), an organization unit (ou) and an organization (o):
uid=%s,ou=people,o=florizel.com. The user抯 ID replaces ?s?after
configuration of the user抯 profile.
-
It's not correct for hosted domains, because uid will be replaced by full email address
uid=user@domain,ou=people,o=florizel.com
So two choices - one is to find a way to configure correctly this in connector deployment progamm
(but docs say nothing about it), or to rewrite BIND operation at LDAP server level (but I cant find how).
P.S. I've found an answer in description of bug 6427345 (about undocumented arguments %user and %domain)
