This content has been marked as final. Show 3 replies
Lots of views, but no responses. Is there any interest out there in LDAP integration ?
I've resolved this issue, I had not been giving the full object path to the new user I was adding to AD.
&inAttrDoc = &inAddDirectoryEntries.AddDoc("Attribute");
&biReturn = &inAttrDoc.AddValue("Attribute_Name", "objectclass");
&biReturn = &inAttrDoc.AddValue("Value", "top");
&biReturn = &inAttrDoc.AddValue("Value", "person");
&biReturn = &inAttrDoc.AddValue("Value", "organizationalPerson");
&biReturn = &inAttrDoc.AddValue("Value", "user");
Originally I had been givning only the user value not the top>person>organizationalPerson>user values. When that was added, I was in business.
Edited by: user632288 on Jul 15, 2009 9:34 AM
I struggling with ldap_search itself. Is there anything need to be enabled to make the business interlinks to work properly?
My command line ldapsearch works perfectly; however ldap_search always return -1 as return status. My exposure and experience in Business Interlinks is not that deep. Any hints?
Before getting to the Interlink itself, is your configuration to the LDAP server complete?
Enterprise Components > Directory Interface > Definitions > Directory Configurations
... and from the server configuration when you access the Test Connectivity page are all the tests successful?
If so then go the the delivered utility Enterprise Components > Directory Interface > Search Directory and build the search you'd like to send through the interlink and run it. Then when that search is successful, look at the code behind the 'Search' button and use it to build whatever process you need.
I've successfully used the interlinks to Search, Add, Modify, and Delete AD users from the HR system.