|
We have some apps that make LDAP queries to allow a user to log in. Picture an “empty” root with two sub-domains. If the app is to be used only in a single sub-domain, i.e. dc=domain1,dc=company,dc=com, it works fine. If it needs to cross over to the other domain we have, though, i.e. dc=domain2,dc=company,dc=com, we’re out of luck. We can’t make the root dc=company,dc=com LDAP query search BOTH sub-domains for the user. Is this a limitation of LDAP, or of the apps that are trying to use it? I suspect it’s the apps, but maybe there’s a global (middleware?) fix someone can suggest?
If any of you are using an app called Kintana and have conquered this problem, I’d especially like to hear from you.
Thanks!
Mark Creamer
|
- RE: [ActiveDir] LDAP in Multi-domain environments Creamer, Mark
- RE: [ActiveDir] LDAP in Multi-domain environments Mulnick, Al
- RE: [ActiveDir] LDAP in Multi-domain environments Gil Kirkpatrick
- RE: [ActiveDir] LDAP in Multi-domain environments Fuller, Stuart
- RE: [ActiveDir] LDAP in Multi-domain environments Creamer, Mark
