Update, after sending me 2 hotfixes that didn't work BMC Support came back and said this was actually "Functioning as Designed" and that they had changed this starting in 7.6.03 to append an identifier to the requestId field in your LDAP vendor form. Because my integration and vendor form was already written with the samAccountName as the identifier field, we had to move forward and implement a workaround to truncate the leading junk off the name when pushing it to the staging form.
SUBSTR($samAccountName$, 6, LENGTH($samAccountName$)) This actually works ok, because surprisingly you can still search/qualify your data as the plugin will find a match of samAccountName=jsmith (for example) on the vendor form even though it presents the data as 00001|jsmith after returning the results. But I agree with Frederick, the cleaner way would have been to leverage the "uSNCreated" attribute as it is always unique. BMC Support recommended using the "cn" attribute which is not a viable solution because it is not unique, it's basically just a concatenation of firstname, lastname. Side note regarding the 15 character maximum, I believe (don't hold me to this) that that was a former constraint with some of the older versions. I want to say they addressed that in 7.1 or 7.5 but my memory escapes me at times. We've not had any issues (so far) using the samAccountName, until the upgrade interjected this identifier into the mix. Thanks. Nate. Nathan Aker ITSM Solution Architect McAfee, Inc. Direct: 972.963.7611 Mobile: 469.644.7402 -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W Sent: Thursday, October 13, 2011 1:29 PM To: arslist@ARSLIST.ORG Subject: Re: Active Directory Integration Issue with 7.6.04 One thing I was told a long time ago (I think it was RUG 2005) was not to map the sAMAccountName to the Request ID (since Request ID is supposed to be <= 15 characters) for a Vendor form on the ARDBCldap plugin. I have always mapped the uSNCreated to Request ID and just had sAMAccountName as a separate field. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Brian Gillock Sent: Thursday, October 13, 2011 1:20 PM To: arslist@ARSLIST.ORG Subject: Re: Active Directory Integration Issue with 7.6.04 ** Thank you for this, Nathan. I was having the same issue. I worked around it by parsing out the userid when I stored it on my staging form like so: SUBSTRC($Request ID$, STRSTRC($Request ID$, "|") + 1, LENGTHC($Request ID$)) -----Original Message----- On Fri, Oct 7, 2011 at 11:42 PM, Uday Joshi <uda...com> wrote: ** Hi Nathan, I am also struggling with similar issue. Has BMC given any bug number for the same? Any workaround possible. Best Regards, Uday -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Nathan Aker Sent: Thursday, October 06, 2011 6:32 PM To: arslist@ARSLIST.ORG Subject: Re: Active Directory Integration Issue with 7.6.04 ** Just got a response from BMC Support. Appears to be a known defect fixed in 7.6.04 SP2 Thanks. Nate. Nathan Aker ITSM Solution Architect McAfee, Inc. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Danny Kellett Sent: Thursday, October 06, 2011 4:31 PM To: arslist@ARSLIST.ORG Subject: Re: Active Directory Integration Issue with 7.6.04 ** Hi, Have you tried cn instead of samaccountname? Do you have any filters configured in your ARDBC LDAP configuration? Kind regards Danny -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Nathan Aker Sent: 06 October 2011 21:41 To: arslist@ARSLIST.ORG Subject: Active Directory Integration Issue with 7.6.04 ** Hello all, We're running into an issue with our Active Directory LDAP integration after a recent upgrade and I'm wondering if anyone else has encountered or is encountering: We have a vendor form leveraging the ARDBC plugin to integrate with Active Directory for people data. The vendor form displays people data, with the unique attribute being the samAccountName attribute. In setting up the Vendor form, this attribute was mapped as the Request ID. When we were on ARS 7.6.00, when I ran a search against the vendor form I would see the samAccountName displayed something like "asmith" for example. After the upgrade to 7.6.04, now when I run a search on this vendor form, the samAccountName is prefixed with 00001|. So for example, where I saw "asmith" before the upgrade I now see "00001|asmith". This is obviously an issue as we are trying to map the samAccountName to the LoginID field in Remedy. Anyone seen this before or know what feature/configuration is appending the 00001 on front? Thanks. 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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
