Listers, I've got a vendor form to pull people data from Active Directory leveraging the ARDBC plugin. This simple vendor form simply exposes the people attributes which are pulled via workflow to a staging form. We setup the samAccountName as our primary attribute... pretty simple. This worked in 7.6.00 and we extracted the login id from the samAccountName attribute.
After upgrading to 7.6.04, the samAccountName attribute on this vendor form displays what appears to be a partial request id then a pipe and then the value we were used to seeing (Like what you see in a join form). Basically it's putting 00001| before the login value. I'm speculating this possibly has to do with new functionality allowing for the setup of multiple OU connections to the LDAP source and this number 1 is for our 1 configured OU, though wasn't this available in 7.6.00? Regardless, does anyone know a way to either configure the ARDBC LDAP settings to not append the request id before the login value, or create a secondary attribute to allow us to pull the clean samAccountName? I don't know that we have another unique attribute to use as the key field for the vendor form. Previous value of samAccountName attribute in vendor form in 7.6.00: swilson Value displayed in samAccountName attriube after upgrade to 7.6.04: 00001|swilson Thanks for any help. Nate. Nathan Aker ITSM Solution Architect McAfee, Inc. 5000 Headquarters Drive Plano, TX 75024 Direct: 972.963.7611 Mobile: 469.644.7402 Web:www.mcafee.com<http://internal.nai.com/division/marketing/BrandMarketing/templates/www.mcafee.com> [cid:[email protected]] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
<<inline: image001.jpg>>
