Hi Nathan,

 

I am also struggling with similar issue. Has BMC given any bug number for the 
same?

 

Any workaround possible.

 

Best Regards,

 

Uday

 

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

 

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 
<http://internal.nai.com/division/marketing/BrandMarketing/templates/www.mcafee.com>
 

 

 

 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 

_attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ 


Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email. 

www.wipro.com

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

<<image001.jpg>>

Reply via email to