Re: LDAP to multiple Active Directory Forests (Domains)

[Baxter, Andrew]

** Todd, What version of operating systems and AR are you using?  This is pretty standard information you should include with any question to the group.   Thanks, Andrew Baxter Manager, Information Technology w. (781) 902-6026 f. (781) 902-6002 From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Bean Sent: Monday, May 15, 2006 4:54 PM To: arslist@ARSLIST.ORG Subject: Re: LDAP to multiple Active Directory Forests (Domains)   Todd, Not sure if you have already come across this, but this is the response to your question from the Knowledge Base on SupportWeb (KB # KM-000000011324):   "Assuming the domains are part of a forrest, then LDAP can refer to each of the individual domains. They need to identify the host name and BaseDN to use. Currently (as of version 6.0.1), there is no way to configure the AREA LDAP plugin to look to multiple LDAP Servers that are in different forests."   If you do not have access to the KB and would like to see the full text of the article, just let me know.   We do not use AREA for authentication, but I have successfully set up the ARDBC plugin to read from separate LDAP directories (using different login information for each) by following the method outlined in KB KM-000000012275, which involves running a 2nd instance of the plugin server (arplugin/arplugin.exe).   HTH,   Thomas   ----- Original Message ----- From: Todd A. Carter Newsgroups: gmane.comp.crm.arsystem.general Sent: Monday, May 15, 2006 15:32 Subject: LDAP to multiple Active Directory Forests (Domains)   Has anyone come up with a method of handling users logging into Remedy from various Active Directory domains? Can I daisy-chain the lookups?  Is there anything in the LDAP setup that prevents it from looking in multiple domains? Thanks. Todd 734.944.8036 [EMAIL PROTECTED] __20060125_______________________This posting was submitted with HTML in it___ ****This e-mail is sent by Hudson Highland Group, Inc., or one of its subsidiaries, and may contain information that is privileged or confidential. If you are not the intended recipient, please delete the e-mail and any attachments and notify us immediately.**** __20060125_______________________This posting was submitted with HTML in it___